Need to use access for this, need some help

[Nelson12]

Hello all!



I hope this is not to difficult to solve, but I have an idea on this but I don't know if its wrong or right or if there is a better way I can do this.

I have an access 2007 server with 10 people connected to it constantly updating it daily. Everyone has a front end on their laptops and I am the only one who can edit and change the back end. Everyone uses a form to input data and and that's it, they can only view the table that the data is entered.

But we have a data that must be approve before it can be entered into the database. I have figured i can make a separate database for this. This data is written up on white boards and is posted on he share server and looked at and it gone through 3 levels or editing and approval. It is then entered into the database. After a few weeks we erase these white boards and start over. So i cant use my existing database to create relationships with this because the data cannot be inside the database yet until approved.

I am looking for a way to solve the constant movement of everyone in the office to have to go up to the white boards to show the status of that data. And I want to use access to be able to do the same job as the white boards that shown the status of each item needing approval.

Any input would be greatly appreciated, thank you.

[Guus2005]

But we have a data that must be approve before it can be entered into the database. I have figured i can make a separate database for this. This data is written up on white boards and is posted on he share server and looked at and it gone through 3 levels or editing and approval. It is then entered into the database. After a few weeks we erase these white boards and start over. So i cant use my existing database to create relationships with this because the data cannot be inside the database yet until approved.

You can create relationships. To suppress the records that are not approved create a table "tblApproved" to store each RecordId which was approved.
When you create a query to show approved records, you only have to link the table to the tblApproved table.

HTH

[NTC]

separate DBs, or separate tables is NOT the way to go......better to add a field to your main table for 'Approved' (or 'Status') - maybe a checkbox or maybe a textbox.... you can enter data and define it as 'Pending Approval'....this will allow you to present it forms, reports with that caveat....but once it is approved you only need to change it status to 'Approved' or maybe to 'Canceled' or whatever...

in the long run it is simple, plus it gives you a history of past data - and if ever anything is Canceled but then reversed back to Pending or Approved it is really simple to accommodate that....

[Guus2005]

separate DBs, or separate tables is NOT the way to go......better to add a field to your main table for 'Approved' (or 'Status') - maybe a checkbox or maybe a textbox.... you can enter data and define it as 'Pending Approval'....this will allow you to present it forms, reports with that caveat....but once it is approved you only need to change it status to 'Approved' or maybe to 'Canceled' or whatever...

in the long run it is simple, plus it gives you a history of past data - and if ever anything is Canceled but then reversed back to Pending or Approved it is really simple to accommodate that....

That is a matter of opinion. Your solution is also possible. I agree that creating a database for this purpose is not advisable.

Enjoy!