Confirmation by other person

[herrgrek]

I am about to create a rather simple database on my department. My boss has however a desire that when one person adds a new product, another person has to verify the change before it can take place. The same thing for an existing product, if anybody want to change some information, another person has to confirm the change before it can take place.

Would be very thankful if anybody has some experience with a similar problem to this.

[ItsMe]

Have all change requests sent to a tblRequests. Then the other users can forward the requests for final update to the master table.

[herrgrek]

Thank you ItsMe! If I understand you right, The tblRequest should look almost the same as the tblProducts table. Guess the best way is to use VBA in this case?

[ItsMe]

It is just an idea. I don't think I have any real world examples. It would probably look like in normal production flow. Front operations would pass a record to back operations that passes it to Back office.

Each workstation adds a user Id and time stamp. There would also be additional columns for yes/no fields so each department/workstation can give approval. So, come to think of it you probably don't need another table but just a query that shows weather or not the departments approved it or not.

You would just have a special query that would only accept a record as "Saved" if it met certain criteria, ie each department marked the Boolean as yes