onthuhlist wrote:
*Although the mere act of opening the front end should NOT cause the
locking file to be created, yesterday this was actually happening. I
wrote a module procedure to close all forms, then called this
procedure from a form button. Therefore, the code could close the
calling form. I put a breakpoint in the code after all the forms had
been closed, and the .ldb file was still there. Even after 5 minutes
sitting there scratching my head (and cleaning up the dandruff
afterward). Well, today I'm trying the same thing, and the .ldb IS
NOW CLOSING! What's up with this? Microsoft Access isn't even
behaving repeatably... Sigh. This is so frustrating! Again, the back
end is on my PC, so it's not a multi-user issue.

Things you can't do with Access:
1. Programmatically resize an embedded webbrowser control.
2. Put a rich text control on a page of a tab control. *

Here's what I'm finding. I run my code to close all forms. Then I put a
breakpoint in the code which is about to copy and compact the backed,
so I can manually watch the .ldb file for the backend database close.
But the .ldb file for the backend database remains open indefinitely,
even though I run the DoEvents method in the code before my breakpoint.
Then, still in debug mode, I click "Reset" to stop code execution, and
the .ldb file finally goes away. Well, I need the .ldb file to go away
WHILE the code is running, so that I can programmatically copy and
compact the backend.

Any thoughts of how to resolve the issue? Again, I've used the DoEvents
method unsuccessfully.



--
onthuhlist
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message675816.html