This part sounds as if one goal would be to use the db as the storage system for a correspondence too. I don't think that is the 'best' way to store correspondence, spreadsheets, digital pictures, etc. I like the regular filesystem for that, it's easier to backup and recover with standard utilities. Eric Wilhelm (ewilhelm@xxxxxxxxxxxxx) wrote: > >The main concept, which you have seen, is to give a link between the database >and programs which have not been specifically intended to utilize it. This >integrates the collaboration environment, making all of the access control, >network connectivity, revision tracking, etc, other benefits, etc fit into >one nice package with a single configuration/administration interface. The >IT and cad managers would love it and the users (document editors and >draftsmen alike) would not really have to even be aware of how it worked, >they would simply need to always work in the one "directory" for each >project. This also creates an automatic archive for the project, giving the >legal documents and other correspondence a place to live and a consistent >method of tracking what happened when, by whom, etc, etc. > >--Eric > -- Brian Johnson This is where my witty signature line would be if I bothered to edit this line :)