[AccessD] Out of a paper bag

Arthur,

You were the one that told me that long ago.  I thought I would allow you to lay claim to it if you 
so desired, without pointing fingers so to speak.  ;)

 >I thought that a progress meter would be a useful class.

I actually do that in a form in my framework.  It turns out that forms are classes that can be the 
visual interface, host code and controls and so forth.  So sure, let's do a progress meter.

The one thing that needs to be understood is that VBA is 'single threaded' meaning that the user 
interface and the rest of the application is all running on a single thread and if something takes a 
long time to execute (a query for example), then the user interface appears to lock up.

John W. Colby

Reality is what refuses to go away
when you do not believe in it


On 2/17/2013 9:48 AM, Arthur Fuller wrote:
> I may have been the originator of that description of your literary
> prowess. You've come a long way, baby! Even with my keen editor's eye, I
> can't see much that warrants change. Keep up the good work.
>
> I don't know if you plan to get to it, but after reading your bit on the
> Timer class, I thought that a progress meter would be a useful class. I'm
> not sure exactly how it would work, but it would pop up a little screen
> with a progress bar that expands to indicate the progress through a task
> such as walking a recordset. I chose that example because as you could
> discover the set-count initially and then as you process the set you could
> call the Increment (or whatever) method to update the progress bar.
>
> Just a thought.
>
> A.