Wortz, Charles
CWortz at tea.state.tx.us
Thu Aug 7 14:01:18 CDT 2003
Lonnie, If your db is open to everyone there is no sure fire way of determining who has accessed the data. If you move the table to a secured db, then you can control who has access to it and you can log each visit. But Access security can be broken easily so this is not a sure fire method either if you stay with Access. However, if you move the table to a db with industrial-strength security such as SQLServer, then you will be able to say with a much higher level of assurance that you know all that access the data. Charles Wortz Software Development Division Texas Education Agency 1701 N. Congress Ave Austin, TX 78701-1494 512-463-9493 CWortz at tea.state.tx.us -----Original Message----- From: Don Elliker [mailto:delliker at hotmail.com] Sent: Thursday 2003 Aug 07 13:31 To: accessd at databaseadvisors.com Subject: RE: [AccessD] Who is linked to my back end? It would probably be managed better in the other direction. Either secure the application/BE files or folders in which they are kept. Then you (or the Big Chief) need not wonder (too much) who's accessing tables - that really is a Big Chief question....boy they can sure ask 'em - "Hey, I want to know everybody who has EVER parked around my parking space- I got a ding in my Beemer!!" _d "Things are only free to the extent that you don't pay for them".-Don Elliker >From: Lonnie Johnson <prodevmg at yahoo.com> >Reply-To: Access Developers discussion and problem >solving<accessd at databaseadvisors.com> >To: Access Developers discussion and problem >solving<accessd at databaseadvisors.com> >Subject: RE: [AccessD] Who is linked to my back end? >Date: Thu, 7 Aug 2003 11:22:21 -0700 (PDT) > >You raise some great issues here John. I thank you again for your >thoughts. > >However, I was reaching a bit in a different. I was wanting to know of >ANYONE and EVERYONE that had a link to a particular table in my back end no >matter if they were using it or not. > >I have an officer of the company wanting to know who could be linked to >a >particular table. It would have likely been via the linked table >manager/wizard. > >Thanks again. > >John Colby <jcolby at colbyconsulting.com> wrote: >AFAIK, JET and only JET "knows" the internals of the Access db. It >creates the lock db and it handles requests for data from an MDB from >requesters such as DAO and ADO. > >It does indeed give one pause. This is a sore point with the use of an >MDB. OTOH, can you "ask" SQL Server who is accessing a given table at >the moment? I don't have the answer to that. Now that someone has >asked, it seems a logical thing to do, or at the very least ask who has >accessed a given table >(historical). The problem is that there are so many paths in to data. A >document in word could do a mail merge. That document could be opened from >a VB front end remotely. "who" is asking for the data? The document? The >user of the machine that used automation to open the document? And if the >request comes from the web... how in the world do you determine who asked >for the data. At best you would get an application as the requester. > >John W. Colby >www.colbyconsulting.com > >-----Original Message----- >From: accessd-bounces at databaseadvisors.com >[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Don Elliker >Sent: Thursday, August 07, 2003 1:34 PM >To: accessd at databaseadvisors.com >Subject: RE: [AccessD] Who is linked to my back end? > > >Not for nothing, but, SOMEthing is writing that LDB and seems to know a >bit about the access to the Db. I wonder if any fields in the system >tables are storing access information? I must say, I have never really >looked to see how the LDB file gets created, etc. -but it gives one >pause,no? _d > > >"Things are only free to the extent that you don't pay for them".-Don >Elliker > > >From: Lonnie Johnson > > >Reply-To: Access Developers discussion and problem > >solving > >To: Access Developers discussion and problem > >solving > >Subject: RE: [AccessD] Who is linked to my back end? > >Date: Thu, 7 Aug 2003 10:25:16 -0700 (PDT) > > > >Thank you John. We don't always get the answer we want, but at least > >we know what direction to go from there. I appreciate you taking the > >time to respond. > > > > > > > >John Colby wrote: > >Boy, now there is a million dollar question. My best guess would be > >no. If you think about it, accesses to the table may not even be done > >via "links" which implies an Access FE. The access to the tables may > >come >from > >VB, a web page etc. All of these could use DAO or ADO. > > > >I think the best that you can do is look at the LDB (lock file) and > >see >who > >is CURRENTLY using the db. This method is far from reliable however > >since there are cases where "user data" is not cleaned out of this > >file when >the > >user shuts down abnormally etc. > > > >John W. Colby > >www.colbyconsulting.com > >-----Original Message----- > >From: accessd-bounces at databaseadvisors.com > >[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Lonnie > >Johnson > >Sent: Thursday, August 07, 2003 12:49 PM > >To: Access Developers discussion and problem solving > >Subject: [AccessD] Who is linked to my back end? > > > > > >In a case of a "back end" holding data and various "front end >interfaces", > >is there a way to determine who or what is linked to the back end? > >Any script I can run on the back end to determine what is linked to > >it and >what > >tables is that other database looking at? > > > > > > > >Lonnie Johnson > >ProDev, Professional Development of MS Access Databases Visit me at > >==> http://www.prodev.us > >