I currently have a form that is connected to an Access database. When I create a new form, a row is inserted into the database and the form is saved to
a SharePoint library.
Once the initial document has been created, I would like the user to "checkout" the form to make changes. While the form is being updated with the new changes, the original production version still exists for reference. The user will then submit their requested changes for a approval (original production version still exists). Once the request is approved, the new document will override the existing production document and the backend Access database will be updated with the changes.
The main issue I run into with this is the Access database. If I make changes to the "request" document but don't initially update the database, I get a data integrity error in SharePoint (database does not match document) when I try to complete the update. If I use SharePoint versioning, I also have problems with updating the table with the correct information if I have to revert to an old version (database does not get updated accordingly).
Do you have any ideas on how I can keep a production doc, revision doc, and my database all updated properly? I would like to have the evolution of the document or a historical record.
Note: I only want the database to contain the production version of the document. Or, it would be okay if the database contained ALL versions of the document, but I'd need a way to only show the production version in a SharePoint view.
Thanks,
Chip