Weird problem - reboot required

  • Thread starter Thread starter Tcs
  • Start date Start date
T

Tcs

I'm asking this question here because I believe my problem is directly related
to my current Access 2000 project. (I know I may be wrong.)

Yesterday and today I've been really beating on my PC, debugging my code. I've
been running and running and running it, over and over. (It reads a text file
and extracts data to build 4 separate tables, using DAO.)

The same thing that happened to me yesterday, just happened again today. All of
a sudden my machine got *really* slow. Then almost non responsive. Lotus Notes
couldn't find the Notes server, Agent couldn't find the Internet, IE couldn't
find the Internet. Right clicking on the Task bar to bring up Task Manager
didn't work. The 'three finger salute' didn't work. Even trying to
reboot...ALMOST didn't work. (It DID work, but took a LONG time, compared to
the 'normal' time.) And all appears to be fine, after rebooting.

My machine is a P4 Gateway with 1256mb RAM, XP sp1, Office 2k, sp3.

Is there something *special* I should be doing when I debug? What should I be
checking for should this happen again? Any ideas/thoughts would be appreciated.

Thanks in advance,

Tom
 
It is just a thought

When you are debugging your code, do you stop execution in the middle? Some
times, when you do it, the Access (or any other program) doesn't release the
variables and files you are working with so, the resources of your machine
decrease on each debug run you do... after a while, there is none to keep the
OS working.

Put your ON ERROR GOTO to work and place the release commands in there for
all files and recordsets you are using. This may help.

If during the debug, you really have to stop the execution... try closing
and reopening your Access one in awhile.

It works for me

Take care

Mauricio Silva
 
I'll try that, thanks.

It is just a thought

When you are debugging your code, do you stop execution in the middle? Some
times, when you do it, the Access (or any other program) doesn't release the
variables and files you are working with so, the resources of your machine
decrease on each debug run you do... after a while, there is none to keep the
OS working.

Put your ON ERROR GOTO to work and place the release commands in there for
all files and recordsets you are using. This may help.

If during the debug, you really have to stop the execution... try closing
and reopening your Access one in awhile.

It works for me

Take care

Mauricio Silva
Click to expand...
 
Back
Top