How do I work around or compensate for the delayed refresh?

[steve728]

I noticed that when I use ADO in the backend of a dataview
form, upon returning to the display the changes are still
not reflected. If I hit my button event (Me.Requery)
immediately I still will not see the changes made. I must
wait about 2-3 seconds before hitting the me.requery
button for it to work. It's very unprofessional for a
client to have to wait 2-3 seconds and then press a button
for the current data to display. Instead he wants the form
to display the new updated record data by itself (even if
there is a 2-3 second delay. Can anyone help me with
this. This issue has been killing me for months!

I use only one public connection object throughout the entire
project. The form uses a stored query as it's recordsource.

Thanks in advance for whatever help you can render!

Steve

 

[jeremie_ingram]

One trick I have used in the past is to create a small pop up form that informs tham that the data is being processed. It appears for a few seconds, then goes away. It doesnt do much but delay the execution of the code, which is neccessary for the proper information to be displayed. It does, however, give them something to look at and adds a more professional application type touch to the GUI.

 

[steve728]

That's exactly what i came up with for the time being. Wow
what a coincidence. I used the timer interval (4 seconds) as the delay time then it closes. There has got to be some kind of work around though. Don't you agree?

Thanks for replying so quickly!

Steve