[AccessD] ODE VBA Error Handler Crashes Access 2000

John
 
I haven't used any of the terrible Win95/Win98/Me lineage of OS's since
NT Workstation was released. 
 
I recommend to my clients that only the NT/2000/XP Professional line be
used for business.
 
I'll look at the Access processes.
 
Thanks.

-----Original Message-----
From: accessd-admin at databaseadvisors.com
[mailto:accessd-admin at databaseadvisors.com] On Behalf Of John W. Colby
Sent: Monday, February 17, 2003 7:52 PM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] ODE VBA Error Handler Crashes Access 2000


>Also when MS Access crashes use Ctrl+ALT+DEL to open Task Manager and
to see that you may have ghost MS Access processes running - remove them
 
This brings up another very real reason why Windows 98/me sucks.  I have
seen cases where instances of Access were hanging around.  They are
visible in the Processes tab of Win2K's task manager but are not visible
in the Applications tab or in Windows 98 / ME.  In A2K you can just look
in the Processes tab, find them, and shut them down.  In Windows 98 /
ME, they can't be seen at all so you don't even know they are still
loaded - until you start running into the swap file that is.  Rebooting
Windows 98 is the only way to remove these ghosts.

John W. Colby
Colby Consulting
www.ColbyConsulting.com 

-----Original Message-----
From: accessd-admin at databaseadvisors.com
[mailto:accessd-admin at databaseadvisors.com]On Behalf Of Shamil
Salakhetdinov
Sent: Monday, February 17, 2003 7:27 PM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] ODE VBA Error Handler Crashes Access 2000


<<<
(2) how to avoid having to log off to correct the 'Locked by Admin'
error.
>>>
Myke,
 
Try to use rotclean.exe after Access crashes - it was here:
 
Internet (anonymous FTP)
      ftp ftp.microsoft.com
      Change to the Softlib\Mslfiles directory
      Get ROTCLN32.EXE
 
Also when MS Access crashes use Ctrl+ALT+DEL to open Task Manager and to
see that you may have ghost MS Access processes running - remove them,
then run rotclean.exe. RotView.exe (from VS6) can be used to see hanging
ROT objects left by crashed MS Access....

HTH,
Shamil

----- Original Message ----- 
From: Myke  <mailto:mmmtbig at bellsouth.net> Myers 
To: accessd at databaseadvisors.com 
Sent: Tuesday, February 18, 2003 2:31 AM
Subject: [AccessD] ODE VBA Error Handler Crashes Access 2000

I've been working on an Access 2000 frontend for several hours --
testing and debugging some reports. I'm in a module looking at a sub
procedure that I just documented. I decide to add an error handler using
the ODE tool from the Add Ins list. I ALWAYS save before I run this.
 
It crashes Access (happens about once a week). When I open the frontend
I was working on and try to repair/compact, I get the dreaded 'File is
locked by user Admin' error.
 
I log off Admin and log on again. Open the app, run repair/compact, and
go back to work.
 
No disaster, but 20 - 30 minutes lost. 
 
Anyone have any suggestions about 
 
(1) why the VBA Error Handler Add-In crashes occasionally, and 
 
(2) how to avoid having to log off to correct the 'Locked by Admin'
error.
 
TIA,
Myke

  _____  

Is email taking over your day? Manage your time with eMailBoss. Try it
free! http://www.eMailBoss.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030217/bb04a8d1/attachment-0002.html>