VB, ODBC AND SQL SERVER. THE SOLUTION TO SPEED PROBLEMS!
After working on this problem for several weeks, I've finally got a VB
program using ODBC to SQL server running fast on a 486dx66 with 8Mb
with a 60,000 + record database.
However, I still have some reservations about the way I've done it.
Anyone want to discuss this?
The way I've done it is to use a local table in an access database.
When the user requires a record, the program executes a query that
load the local table from and SQL view.
When the program writes the record, it generates an SQL update query
on the fly, and applies it to an updateable query in the same
database. All of the tables are attached to the SQL server database.
My main resaervation is that this seems like a real mess.
What are yours?
Sid/
