Dear Sir or Madam,



I have created a field on one of my tables that records MachineIDNames 

when the user makes changes to record through a form. Unfortunately, I 

have more and more people with write access to the database and they are 

now inputting information directly into the database(bypassing the 

forms).  Would you  have any surggestions on how to keep a record of these 

users, short of limiting the user "write" privelages.



Q: Can I have a seperate table that only keeps track of all users who log 

into the database-Write or read access

I don't believe access  has an event tied to a table - so "short of limiting

the user write privelages" may not be possible. I will be looking for other

peoples answers here.

The solution I use is to split the database into two and link them,

(application and backend)  using the wizard. Then secure the data component,

and pass a password in the link so that only the application can use it,

(and me with the password). In this way they can only change the data by

using the application. My log file entries are generated by events on forms

in the application, and note the network UserID of the user - in our

organization their machine IDs are mystical. In the backend DB (the data) I

have one start-up form which displays for 10 secs, tells them they do not

have access, then quits.



If any of this helps I will be happy to send sample code, but the key is the

users requirements, and if they demand access to the tables then you have a

problem.



----- Original Message -----

From: "KennethMungwira" <KennethMungwira@Y...>

To: "Access" <access@p...>

Sent: Tuesday, December 18, 2001 8:15 PM

Subject: [access] User Names:





> Dear Sir or Madam,

>

> I have created a field on one of my tables that records MachineIDNames

> when the user makes changes to record through a form. Unfortunately, I

> have more and more people with write access to the database and they are

> now inputting information directly into the database(bypassing the

> forms).  Would you  have any surggestions on how to keep a record of these

> users, short of limiting the user "write" privelages.

>

> Q: Can I have a seperate table that only keeps track of all users who log

> into the database-Write or read access

--0-922546549-1008774532=:29179

Content-Type: text/plain; charset=us-ascii





 Please send me some sample coding?

 

Thank you-Kenneth Mungwira

  David Chapman <luckychap@b...> wrote: I don't believe access has an event tied to a table - so "short of limiting

the user write privelages" may not be possible. I will be looking for other

peoples answers here.

The solution I use is to split the database into two and link them,

(application and backend) using the wizard. Then secure the data component,

and pass a password in the link so that only the application can use it,

(and me with the password). In this way they can only change the data by

using the application. My log file entries are generated by events on forms

in the application, and note the network UserID of the user - in our

organization their machine IDs are mystical. In the backend DB (the data) I

have one start-up form which displays for 10 secs, tells them they do not

have access, then quits.



If any of this helps I will be happy to send sample code, but the key is the

users requirements, and if they demand access to the tables then you have a

problem.



----- Original Message -----

From: "KennethMungwira" 

To: "Access" 

Sent: Tuesday, December 18, 2001 8:15 PM

Subject: [access] User Names:





> Dear Sir or Madam,

>

> I have created a field on one of my tables that records MachineIDNames

> when the user makes changes to record through a form. Unfortunately, I

> have more and more people with write access to the database and they are

> now inputting information directly into the database(bypassing the

> forms). Would you have any surggestions on how to keep a record of these

> users, short of limiting the user "write" privelages.

>

> Q: Can I have a seperate table that only keeps track of all users who log

> into the database-Write or read access















---------------------------------

Do You Yahoo!?

Check out Yahoo! Shopping and Yahoo! Auctionsfor all of your holiday gifts!