On No Data retry later

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Due to the timing, there are times that the data is not available for the
report, but will be there in a couple seconds.
I understand and is working on to identify the data holdups from the source.
Now I want to implement some things in the front end that will requery the
record source couple more times when the first try ended up with no data.
I have the report_Nodata () cancel=true, as well as catch the 2501, then
msgbox in place. How do I achieve the retry?
One way I can think of is to add a label/pointer before the
docmd.openReport, and use a counter to control how many time to go back
there. This is not a pretty solution.

Thanks!
 
homer said:
Due to the timing, there are times that the data is not available for the
report, but will be there in a couple seconds.
I understand and is working on to identify the data holdups from the source.
Now I want to implement some things in the front end that will requery the
record source couple more times when the first try ended up with no data.
I have the report_Nodata () cancel=true, as well as catch the 2501, then
msgbox in place. How do I achieve the retry?
One way I can think of is to add a label/pointer before the
docmd.openReport, and use a counter to control how many time to go back
there. This is not a pretty solution.
Click to expand...


That sounds like a good approach to me. You have to have a
counter to know how many times you've tried it and you have
to have some kind of Resume when you catch the 2501 error.
Seems to me that adding another mechanism on top of that is
just adding unnecessary complications.
 
Back
Top