Quote:>Wow, what a selection of tools in VB6 Prof. ver! Problem is deciding
>which tools are best for my situation. Hope someone can help with this.
>The application uses a database with a number of tables. The tables
>store information about settings for devices connected to the serial
>ports. One of the tables also stores readings from the devices. Now my
>questions. This application is not a C/S situation where I'm getting
>data from a database, but I may want to make a database that can be read
>by other computers on the network (think of it as an appointment
>database so others can see what my schedule is). The number of users
>trying to see the database will be very limited. Because I am storing
>readings in one table, I need to make db operations as fast as possible.
>I need to get a demo going as soon as possible, so learning time and
>coding time are as important as access speed. Now the questions.
>1. Which database should I use - Access, etc?
Limited users, I would probably say access, as long as the db is not
overly huge. An RDBMS is better for large number of users and/or large
data stores.
Quote:>2. Which technology is best - DAO, RDO, ADO?
I would vote ADO in general. Reasoning, better support and quite easy
to program. For full functionality, you can use OLE DB, but only if
you really need to go down this path (headache).
Quote:>3. Should I use a data control or use code to define the recordset, etc?
I started with ASP, so I prefer coding my own recordsets. However, the
data tools in VB are quite nice.
Quote:>4. Where is the best source of consise, but complete information on
>working with databases in VB? The help files make me crazy, and most
>general books begin with "Databases is such a large subject... Thus, we
>can only cover...". I don't have time to read a 400+ page book right
>now (nor do I have 21 days ;-) ).
>Thanks,
Depending on what you are attempting to accomplish, many of the ASP
sites have some nice ADO information. Of course, the downside is most
ASP programmers use inline code instead of procedures, but I am sure
you can overcome that hurdle. Also, ASP aims for late binding, which
is not necessarily the best method to handle this one.
If you are already a programmer with some experience, the 'in a
nutshell" book on VB/VBA is nice for quick pointers. The real question
is how complex is the work you are attempting. It would be foolish for
me to aim you in a particular direction without understanding more
about the specs.
If RAD is most important, here is a bit of a way to get a basic demo
up quickly that might seem a bit unorthodox:
Download a copy of Drumbeat and build it as an ASP web app. If the
queries, etc., work, you can either leave it as a web app, or transfer
the VBScript code to VB. You will need to type your code (DIM whatever
AS string, etc. -- VBScript does not allow using types), but this is a
small price to pay for a rapid demo.
GB
MCSE, MVP (FrontPage)
***********************************************************************************
Think Outside the Box!
***********************************************************************************