NT & Me...

[Randomblink]

Ok...
I am closing my db using vb code.
The problem I am having is:

Sometimes (and sometimes not), when the db closes, I have a floating .ldb file of the db that sticks around.

You can't delete it (sharing violation) and you can't open ANY other db's while it exists.

It goes away if I reboot.
OR...

If I [ALT + CTL + DEL] (In an NT environment), and I goto to the Task Manager, I will see an MSACCESS.EXE floating under processes. I have to hard-end process that MSACCESS.EXE THEN I have to manually delete the .ldb file. What am I doing wrong?

What can I do to clean that up? Can someone help me?

 

[bradcccs]

(I hate posting directly after Pat - cos the problems probably already fixed) - However:

As a stab in the dark: Are you using any conditional formatting?

I had this exact circumstance occuring with one of my db's.

Turns out (after lots of problem solving) that the conditional formatting of one of my datasheets was causing the problem.

The condition statement was based on a text output, and then formatted accordingly. (eg: ="In" backcolour = green etc) The formatting worked great, but on closing the db, I had your same symptoms.

On changing the conditional formatting statement to a numerical output (eg: [FormInOut].value = 1 backcolour = green) the formatting was still correct (a little slower) but the symptoms you describe were corrected.

This problem is reconstructable, and is persistent under the circumstances. I have not found any reference to this issue with MS.

If you are not using conditional formatting, i apologise for wasting your time, but thought it too similar not to mention

Cheers

Brad.

 

[Randomblink]

Yippee!

Pat, first try after implementing your option worked!

I was using DoCmd. Quit to close down.
Now, Application.Quit acQuitSaveAll
First try, it's working...!!!!
Thanks

Brad, since I am not sure what you mean by your conditional formatting...I have to assume I am not doing it. Thanks for the help anyway...