Who accessed the database

[Guest]

I want to run a report that will tell me who has accessed the database. Is
there a way to do that? Thanks.

 

[RBear3]

Only if you have been logging that data. You would need to create a table
and store logins/logouts.

 

[Guest]

I know how to create a table but how would I have it store logins and logouts?

 

[Tony Toews [MVP]]

I want to run a report that will tell me who has accessed the database. Is
there a way to do that?

Not retroactively. Besides anyone can access the tables directly and create their
own queries. If you need that kind of audit trail you want to move the data from MDB
to SQL Server or equivalent and log all queries.

There's a simple example at
ACC2000: How to Create an Audit Trail of Record Changes in a Form
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q197592

Audit Trail - Log changes at the record level at:
http://allenbrowne.com/AppAudit.html
The article addresses edits, inserts, and deletes for a form and subform.

Modules: Maintain a history of changes
http://www.mvps.org/access/modules/mdl0021.htm
The History Table routine is designed to write history records that track the changes
made to fields in one or more tables.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Aaron Kempf]

well if you used SQL Server-- then you could run PROFILER in order to
determine a full audit log-- of who does what and when-- without writing a
single line of code

this type of functionality is not available in MDB format

MDB has been depecrated; MDB hasn't had any improvements for the past 10
years

 

[Aaron Kempf]

WRONG!
she just needs to use SQL Server

Only if you have been logging that data. You would need to create a table
and store logins/logouts.

--
Hope that helps!

RBear3
.

 

[Aaron Kempf]

NOPE

you just need to run SQL Server and use SQL Profiler

 

[Aaron Kempf]

well-- WRONG

even retroactively; you can use products such as LogExplorer in order to
view the LOG of a database

in other words-- SQL Server has TWO ways to do this; and Access has NONE

 

[dbahooker]

CORRECTION!

Using VBA audit trail is all fine and good-- until someone disables
VBA

move to SQL Server and use TRIGGERS


or jsut use PROFILER
or just parse the transaction log yourself

 

[Aaron Kempf]

you've got 3 options

SQL Server PROFILER
SQL Server TRANSACTION LOG
SQL Server TRIGGERS

Accsss MDB doesn't support an audit trail like this