Revision Tracking - program concept

G'day All I'm writing an application for an intranet environment. At the moment I'm writing a document control system. The intention is that people will be able to check in documents (generally created in MS Word from templates) and the app will upload them to the server. The process related to this involves other people then checking the documents back out and making appropriate changes based on their responsibilities and then checking the documents back into the system again. What I would like to do is keep track of each revision of these documents (ie. actually provide a capability to review earlier revisions, or, indeed, revert to earlier revisions). At this stage I am planning to track information about each document in an SQL table but not actually store the binary data in the table (there are additional reasons behind this). The only solution I've come up with that will easily implement some sort of revision system would be to store only the last five, for example, revisions and then use duplicate SQL tables to store older iterations of the document with suitable links in the SQL back to the current version. Can anyone suggest an alternate approach that will let me do this? More from a program logic point of view than from an actual code example point of view really. I guess that makes this close to off-topic but there you go - hopefully it won't be considered too out of place. CYA, Dave ----------------------------------------------------------------------- Outback Queensland Internet - Longreach, Outback Queensland - Australia http://www.outbackqld.net.au mailto:dfreeman@outbackqld.net.au -----------------------------------------------------------------------