Testing for Database Task Complete

[cmgrn]

I am writing a VB6 payroll program using Access97 for my database on a network. My problem is odd errors that seem to have no clear relationship to the place the program stops BUT always go away if I put a 1-5 second pause in front of the database operation where the program stopped. I think I am running past the networks ability to complete a previous operation before I hit it with more but am not sure.

A typical example is loading a grid on Form_Load. When opening a form, sometimes the grid fills properly but occasionally the grid will be empty. Retrying the form over and over produces content or no content.

Is there a way using VB6, Access97, DAO and/or ADO to check if a previous database operation (like loading a grid or deleting the contents of a work table) is complete before I let my program move on to the next step?

I believe this is a network problem because in every case, by adding a 1-5 second pause in front of the trouble area, I get the correct results. Remove the pause and I can get spotty results.

Thanks for your time and consideration in advance.

 

[hymn]

Have you thought of splitting the db and putting the front end on your local machine and the back end on the server

Hope this helps
Hymn

 

[cmgrn]

Thanks for the quick response. No, I am not familiar with the frontend/backend design. I am basically using VB6 with DAO and ADO connections and then using SQL strings to Set, Open, use, Close, Set=Nothing tables as I need them. The VB6 exe will then be individually installed on the clients' machines who need to work with payroll. The Access97 database is on a network server. We are not using bound tables either because of all the error checking being done on content and relationships between fields. We do not use Access97 forms or reports or macros.