Access Run-time Issue

[Markus]

Here's what we have:
Using Access 2000 Runtime, we have built a custom app for our sales force. A
few months ago, we started seeing this issue on some of our clients.
When a user logs in to our system, it lets them in fine. Then they will
close out at some point and try to go back in. It looks as if it will open
up Runtime Access again and open up our database, but it does not.
If you at that point look in the Task Manager, you see MSACCESS.EXE as a
running process consuming anywhere from 25 MB -> 50 MB worth of memory.
However there is no way to switch to that instance of access. It is closing,
but the task is not ending correctly.

Has anyone ever seen this issue? How did you fix it?
Thanks,
Mark

 

[Tony Toews]

Using Access 2000 Runtime, we have built a custom app for our sales force. A
few months ago, we started seeing this issue on some of our clients.
When a user logs in to our system, it lets them in fine. Then they will
close out at some point and try to go back in. It looks as if it will open
up Runtime Access again and open up our database, but it does not.
If you at that point look in the Task Manager, you see MSACCESS.EXE as a
running process consuming anywhere from 25 MB -> 50 MB worth of memory.

Access minimizes to Windows 95/NT toolbar instead of closing
http://www.mvps.org/access/bugs/bugs0005.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm