Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
DBF Monitoring
- Thread starter PeterL
- Start date
Mike Gagnon
Programmer
PeterL
You could use a low-level file functions, create a text file (transactions.log), and keep track of every move the user makes. For example when he saves a record, open the text file and record the action, the user name and the time he saved the file. Mike Gagnon
You could use a low-level file functions, create a text file (transactions.log), and keep track of every move the user makes. For example when he saves a record, open the text file and record the action, the user name and the time he saved the file. Mike Gagnon
darrellblackhawk
Programmer
I don't know of any tools that will do that. Maybe someone else does. If not, you'll unfortunately have to re-structure the app.
If not, and you are using W2k, you may be able to perform after the fact analysis using the 'Change Journal', but I'm not sure.
You can find information about this in the W2k SDK under 'Files systems'.
I had to perform the same thing in an app and placed the tracking logic in the application, but I'm sure you don't want to do a major re-write.
Oh- If the app is using all Database containers, and there isn't a tool available, you may be able to simplify the task by performing the tracking function via stored procedures and/or triggers(Triggers will be the easiest since they will fire every time without explicitly calling them.) Just a thought.
Darrell 'We all must do the hard bits so when we get bit we know where to bite'
If not, and you are using W2k, you may be able to perform after the fact analysis using the 'Change Journal', but I'm not sure.
You can find information about this in the W2k SDK under 'Files systems'.
I had to perform the same thing in an app and placed the tracking logic in the application, but I'm sure you don't want to do a major re-write.
Oh- If the app is using all Database containers, and there isn't a tool available, you may be able to simplify the task by performing the tracking function via stored procedures and/or triggers(Triggers will be the easiest since they will fire every time without explicitly calling them.) Just a thought.
Darrell 'We all must do the hard bits so when we get bit we know where to bite'
Hi !!!
Like Mike I had in one of my application 'spy table'. When somebody open the some table, update or write record in this file i write who, when, where and what to do. Because of the users often say: 'I don't nothing, but it's bad'.
Monika Kind regards to you all from Warsaw !!!!!
Like Mike I had in one of my application 'spy table'. When somebody open the some table, update or write record in this file i write who, when, where and what to do. Because of the users often say: 'I don't nothing, but it's bad'.
Monika Kind regards to you all from Warsaw !!!!!
Make a log table with user,transacts...etc.
-When addition is occured and user saves - Add a record to
that table including name,id etc of that user.
-When user modifies - copy original record to file x.
when user saves copy modified record to y.
compare fields if any field does not matches, add that
field to a string and append that to log table by saying
field a,b,c changed on xx date, by zz user etc.
-When delete occurs simply add 'deleted by zz user on xx
date
Bada
-When addition is occured and user saves - Add a record to
that table including name,id etc of that user.
-When user modifies - copy original record to file x.
when user saves copy modified record to y.
compare fields if any field does not matches, add that
field to a string and append that to log table by saying
field a,b,c changed on xx date, by zz user etc.
-When delete occurs simply add 'deleted by zz user on xx
date
Bada
- Status
Similar threads
- Locked
- Question
