You have two options here. Since this is Microsoft Access you are talking about (not just any database software) your first option is to use the public activeX methods with invoke node to program the database. IMHO, this is not the best way to read/write a database. I don't know if any other DB has public activeX methods. maybe, maybe not.
Option 2 is to get the SQL toolkit. SQL is an ANSI standard programming language for databases. If its a true database, it supports SQL. Your code will then be portable to other databases (if you should change in the future) and all the work you will be doing will give you (personally) a new tool. Probably best of all, you won't be locked into Billy G.
SQL allows the database to do such things as searching, sorting, linking, join
ing, etc, etc. for you. This means your program will not have to do this work. Network the database and not only do you save time in development (not having to write some code) but save runtime because the database will be on a seperate machine. Therefore another processor will be working for you too! Only the results come over the network, not all the data resulting in time savings there too.
While you're at it, look into SQL server 7 from Microsoft or any other true database server system (Mysql is a free system along the same idea as Linux is to OS'es). Access isn't a true db system. It's really like a front end for non-techies to access the data in databases. Its what i have to use at my job, it will work. But as i've investigated databases and the such (taking a SQL course too) i've learned i'm missing alot not having a centralized DB server to do things like creation, admin, security and the such. Access leaves all this up to the individual and the individual database.
Again, it works for us currently, there are only 4 of us developing. This may be good for you too. Just some FYI.
Good luck.
Jared
