Originally Posted by
rpeare
What is your document numbering system. I agree with micron on most of what he's said. For ISO documents everything I've seen is a document number and a revision number, they don't (didn't?) care about the internal revisions the last time I knew anything about it, only what revision was currently in use.
If you are using internal 'sub revisions' and want to track them I would think you'd need another level
Document number ---> Revision Number ----> Revision Step
so you could contcatenate these to be something like 123456.5.1
After reading this entire post there are also a bunch of undefined things which I would think critical:
How are you getting the files to and from the clients? If you are using an FTP site are you using a naming convention that will help you locate files? For instance if you were to name the files you're sending your clients with the internal document number and a tag like
123456_5_1_Outgoing.pdf
and they would respond with their changes in a word document (or other document) with a file labeled similarly:
123456_5_1_Comments.docx
it should be trivial to connect your individual documents/revisions/revision steps to your data. But getting that kind of cooperation from your clients might be difficult.
Secondly as previously mentioned, if your intent is to actually store the documents in your database, do *not* use MS access as your back end. If your business is of any size at all the documents will quickly make the database unusable as MS access tends to start having problems around 2gb in size.
Also like Micron said, I do these sorts of projects for payment and what you're after is *not* a simple one asking someone to do it for you without paying them, which seems to be the gist of some of your posts, is not reasonable. if I've misinterpreted your posts to be asking for someone to do it for you I apologize just giving my 2 cents worth.