M

[Guest]

I thought I had posted this question on 01.09.06 however I am unable to find
it listed so please forgive me if I have duplicated.

I have an access table HYInReg which uses entry and edit forms to store
records.

My requirement for our

 

[Guest]

I thought I had posted this question on 01.09.06 however I am unable to find
it listed so please forgive me if I have duplicated.

I have an access table HYInReg which uses entry and edit forms to store
records.

My requirement for our QMS (Quality Management System) is for a form to be completed requesting a deletion from the records in the above table. I would like the user (using the form) to select the record and confirm it i the correct one and then to add additional information usach as 'request date' ' person making request' and 'reason for request'. I would like then for ALL the information to be passed to another table.

I would then like to view the entries in the table (as administator / no
users should use this) via a form (preferably the same as previous) then
again add additional information such as 'date of deletion' Thus resulting
in a table of deleted records showing, who, what, why, where and when.

Could anybody please explain how I can achieve this, I can creat tables and
forms and follow step by step instructions but do not have an indepth
knowledge of VB coding. Many thanks in advance for all your help.

 

[BruceM]

If you are going to all that trouble to document deletions, why delete at
all? Or are you talking about moving the records, so that they are not
really deleted but more like archived? In either case you could probably
achieve your aims by marking the record as Archived or some such thing. For
securing the records you have options including user-level security and/or
splitting the database. With a split database you could have a different
front end (forms, etc.) for the users and the administrators.
If you really need to delete the records you could use a delete query; if
you need to move the records you could use an append query followed by a
delete query. Help has more information about botht of these, or more help
can be found in this forum, but for now your exact intentions are a little
unclear, so a detailed answer may miss the mark.

 

[Guest]

Thank you Bruce for you reply; I have given your comments some thought and
have decided to approach the whole record trail from a different angle which
would require less forms however I may be posting some specific requests for
VB code in the future to help me achieve this. Again many thanks at least I
now have a plan of action. Sue