Re: Front End/Back End DBs?

From: onthuhlist (onthuhlist.16w1g7_at_mail.mcse.ms)
Date: 05/26/04 

Date: Wed, 26 May 2004 11:11:19 -0500

Douglas J. Steele wrote:
> [B]"onthuhlist" <onthuhlist.16u6s1@mail.mcse.ms> wrote in message
> news:onthuhlist.16u6s1@mail.mcse.ms...[vbcol=seagreen]
>
> You should only see the locking file (LDB) if you're actually working
> with
> the data: running a query, opening a form that's looking up data in a
> table
> (either as a bound form, or say combo boxes bound to a query) or the
> like.
> The mere act of opening the front end should NOT cause the locking
> file to
> be created.
>

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. 

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