-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 10 January 2003 10:17, Kevin Anderson wrote: > Since I have no MS server, I suspect that I'll have a hard time > implementing SourceSafe.
heh... the turn around judo lock in chop. "welllll... since you're running application A, we're going to force you to use application B too!" > CVS does the same thing as SourceSafe, but will it work correctly with > Microsoft Products such as Access 2K. not as automatically, i'm sure. from their website: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnacc2k/html/srcctrl.asp "Each Microsoft Access query, form, report, macro, and module is stored as a text file in Visual SourceSafe. When you get or check out one of these objects, the Access Source Code Control add-in copies the text file from the Visual SourceSafe project to a working folder on your machine. Microsoft Access then imports the text file into your Microsoft Access database, turning it into a Microsoft Access object (query, form, report, macro, or module). Similarly, when you add a Microsoft Access object to Visual SourceSafe, Microsoft Access exports the object to a text file in the working folder. The file is then added to the Visual SourceSafe project by the Access Source Code Control add-in. All other Microsoft Access objects, known as the Data and Misc. objects (such as tables, relationships, command bars, database properties, startup properties, import/export specifications, Visual Basic for Applications project references, Visual Basic for Applications project name, conditional compilation arguments), are stored in one binary file" i would hope you could use some scripting (vbscript?) to automate the export/import part of this and if so, then you'd be good to go for tha tpart... CVS works w/text files just fine. it's the binary file that would suck, as you can't do diffs (though everything else works). on a big DB it will end up taking up a LOT of disk space. in the SS/Access solution they implement locking such that only one developer at a time can be working on the item they have checked out which helps with the requirement for the binary file. but it isn't pretty, and pretty much makes the concept of "source control" a joke for group projects. looking at how the entire Access <=> Source Safe process works as described on MSDN: it's a horrible hack(-job). are you sure you can't use a better product? or just stay with Access 97? - -- Aaron J. Seigo GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 "Everything should be made as simple as possible, but not simpler" - Albert Einstein -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+HxFI1rcusafx20MRAqokAKCTnn5HQIxSRbCtule0Wwk/JA7SQwCeIZOQ AaiayCXYafFEPFRilu90yL4= =AxA3 -----END PGP SIGNATURE-----
