Question/comment regarding LDB file in BE/FE scenario

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Amit - 04 Aug 2005 17:13 GMT

MS Access 2000, Windows XP
======================
Hi,

I observed something regarding the LDB file, and was wondering if this is
the way it's supposed to work.

I have a database split into BE and FE, both of them in separate folders.

1. When I open the BE *exclusively*, no LDB file appears.
2. When I open the BE normally (not exclusively), LDB file appears.
3. When I open the FE, I get an LDB file in both folders (BE and FE).

Thinking about it, that does make sense, since LDB file is primarily used
when more than one user is accessing the same file. So, if someone is opening
the file exclusively, there is no need for an LDB file.

Well, I started with a question, but it seems more like a comment, as I
think I figured it out :)
Still, if someone would like to add to the explanation, another opportunity
for me to learn more.

Thanks.

-Amit

Reply to this Message

Albert D.Kallal - 04 Aug 2005 17:32 GMT

Yes, you are on the right track.

>3. When I open the FE, I get an LDB file in both folders (BE and FE).

Yes, the above makes sense, since often, the FE will also (or can) have
tables.....

As a interesting note, the workgroup file (which is a mdb file, and can be
opened by ms-access by the way) also creates a locking file. This means that
you should NOT create a workgroup file with the SAME name as your FE/BE. So,
if you are using security, then in effect 3 locking files will be created
when you run your application.

Also, since these locking files can take a LONG time to create, that is why
keeping a persistent connection open to the BE at all times can increase
your performance by a LARGE amount (since those slow file creates don't
happen).

So, in your startup code, open a table in the back end...and keep it open
(this will remove delays in your software).

Signature

Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com
http://www.members.shaw.ca/AlbertKallal

Reply to this Message

Amit - 04 Aug 2005 18:01 GMT

> As a interesting note, the workgroup file (which is a mdb file, and can be
> opened by ms-access by the way) also creates a locking file. This means that
> you should NOT create a workgroup file with the SAME name as your FE/BE.

Ah, good to know. I was thinking of creating a separate folder on the server
for the MDW file, and will make sure to give it a different name.

> Also, since these locking files can take a LONG time to create, that is why
> keeping a persistent connection open to the BE at all times can increase
[quoted text clipped - 3 lines]
> So, in your startup code, open a table in the back end...and keep it open
> (this will remove delays in your software).

I have an unbound form that opens up when the users open the FE (startup
form). This form uses a query in a combo-box, and this form remains open all
the time (I make it invisible when other forms are open).

Would this serve the same purpose, or would it be better to have a bound
form, open it and then make it invisible?

Thanks, Albert.

-Amit

Reply to this Message