Security Help - Desparate!!!

[Adriana]

I posted a question, but no one ever got back to me so I figure I'll try
again.
I used Access' security feature which is awful and I suggest to other users
to NEVER use it.

What I need is for users to log in using their Windows LogIn ID. Based on
this ID, they can only change the record ina form that they created These
change should be stored in something like a History table (i.e. audit table)
with who changed the record, date/time stamp and what change, deletion or
insertion occurred. I tried Allen Browne's example, "Creating an Audit Log"
but I can't get it to work. is there a simpler or different way? I'm
grasping at straws already. Someone, please help!

 

[Lisab]

This may help
http://allenbrowne.com/AppAudit.html

 

[Adriana]

Thank you for replying, but Allen Browne's approach did not help and was
tricky and convoluted. An I.T. guy helped me here at work and it was much
shorter than Allen Browne's way with less run-time errors. I don't recommend
Allen Browne's approach, personally.

 

[Douglas J. Steele]

Many, many people have used Allen's approach and haven't encountered
run-time errors.

If you think your solution is so much better, why not post it so that others
can benefit?

 

[Adriana]

I'm still in the process of perfecting it so I'll try to post it when it's
finished. I have a special function on it, so I'll have to remove that for
normal use. Our I.T. guys all say Allen Browne's method has caused many
user's problems with run-time errors and other issues, but hey, if it works
for others and they don't have run time errors...more power to them.