I have a user control inside a data repeater linked to a physical Access table via an ADO data control all on the same form.
The user keys some text into a text box and presses a button which kicks off my VB code to create a new set of output records in the ADO data control table. The code is fine and does what it should - except that the database update process doesn't complete before the code to redisplay the data repeater. Therefore the user can only see the results if they click a button that requeries and refreshes the data control once the extract rebuild has completed!
So the database is still doing the update or hasn't flushed it's update buffer or something else (!) while the application thinks all is done.
If I put a msgbox inside the routine (so that the VB code is held up) and clear it immediately it comes up, the requery shows the records in place.
What can I check to see what is going on and to hold up the requery until the update is complete?
The user keys some text into a text box and presses a button which kicks off my VB code to create a new set of output records in the ADO data control table. The code is fine and does what it should - except that the database update process doesn't complete before the code to redisplay the data repeater. Therefore the user can only see the results if they click a button that requeries and refreshes the data control once the extract rebuild has completed!
So the database is still doing the update or hasn't flushed it's update buffer or something else (!) while the application thinks all is done.
If I put a msgbox inside the routine (so that the VB code is held up) and clear it immediately it comes up, the requery shows the records in place.
What can I check to see what is going on and to hold up the requery until the update is complete?
