I was intending to use it from one of the front-end programs. if the user
calls the form stored on the back-end while in the front-end, will it
reference the front-end or the back-end?
> The LDB viewer application will work just fine on linked databases. But if
> you're using it with the front end instead of the backend database, that is
[quoted text clipped - 10 lines]
> > the information is to determine appropriate times to compact the backend
> > tables.
Forms shouldn't be in the backend: they should be in the frontend.
In normal usage, you should have 2 separate lockfiles. There'll be one for
the frontend that'll always be open (in the same folder as the frontend, so
on the user's harddrive if you've done things the recommended way), and one
for the backend that should only be open while users are actually connecting
to the data.
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(No private e-mails, please)
> I was intending to use it from one of the front-end programs. if the user
> calls the form stored on the back-end while in the front-end, will it
[quoted text clipped - 19 lines]
> > > the information is to determine appropriate times to compact the backend
> > > tables.
prhood - 19 Jan 2005 18:23 GMT
So I'll return to my original question. How can a user on the front-end
determine who else is accessing the back-end tables?
> Forms shouldn't be in the backend: they should be in the frontend.
>
[quoted text clipped - 39 lines]
> backend
> > > > tables.
Marshall Barton - 19 Jan 2005 21:03 GMT
>So I'll return to my original question. How can a user on the front-end
>determine who else is accessing the back-end tables?
The LDBuser reoutines accept a path argument that specifies
which database to lookk at.
You can determine the path to a linked table in another MDB
by examining its Connect property.
path = Mid(CurrentDb.TableDefs!linkedtable.Connect, 11)

Signature
Marsh
MVP [MS Access]