Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Modules / DAO / VBA / January 2005

Tip: Looking for answers? Try searching our database.

Determining Users on Linked backend Database

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
prhood - 19 Jan 2005 17:33 GMT
I am working with a database linked to a "backend" database which is also
accessed by other users. Is there any method of determining which of these
users is currently accessing the backend database. The lbd viewer
applications apparenetly don't work on linked databases. The only method i am
aware of at the moment is the "brute force" approach of having each uiser
"log-in" to the backend when their application starts. My reason for needing
the information is to determine appropriate times to compact the backend
tables.
Paul Overway - 19 Jan 2005 17:43 GMT
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
the problem.

Signature

Paul Overway
Logico Solutions
http://www.logico-solutions.com

>I am working with a database linked to a "backend" database which is also
> accessed by other users. Is there any method of determining which of these
[quoted text clipped - 6 lines]
> the information is to determine appropriate times to compact the backend
> tables.
prhood - 19 Jan 2005 17:55 GMT
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.
Douglas J. Steele - 19 Jan 2005 18:08 GMT
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]

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.