A little cryptic, perhaps?! For the OP: your code should execute
DoEvents every few seconds - if your code is looping, which most code
that runs for this long will be doing, you need to put the DoEvents
call somewhere where it will be executed about that often. If your
outer loop is going significantly faster than that, integer divide the
loop counter by something appropriate and execute DoEvents every time
the result changes.
On Mon, 21 Jun 2004 14:54:02 -0700, medialint
<(E-Mail Removed)> wrote:
>Use:
>
>DoEvents
>
>"thriveni" wrote:
>
>> I am currently using Access 2000.
>>
>> Whenever I am running my program that sometimes takes 20 -
>> 30 minutes to finish, and I click on the mouse to do
>> something else the running program goes into the 'not
>> responding ' mode. That is till the access process has
>> finished running I cannot use the machine for anything
>> else. Is this just an ACCESS feature or can I change some
>> settings to disable this.
>>
>> Thanks in advance for any help.
>>
>>
Please respond to the Newsgroup, so that others may benefit from the exchange.
Peter R. Fletcher
----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---