Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
I'd do as follows: - Put the database into a zipfile, mdb files compress well - Put the zipfile into a subfolder all by itself in the project module - Add and commit it so it is in the repository - Whenever you do change the structure of the database, then pull the old mdb file out of the zip, do the changes and put it back in. - Then commit the zipfile This way the database will be in the repository for safe keeping and the file will not be changed in daily use so it will not be autocommitted either. We do it in a different way ourselves since we moved away from Access, but for Access databases we keep the one that is used for our distributions in a separate folder in CVS (not zipped though). This is what we update when needed and this is where the setup engine gets the database from. With SQL-Server we do it differently. Here we have moved to a sql script that creates the database on the target system. This script is purely text and so it can be easily versioned in CVS. The big advantage here is that it is possible to diff versions against each other and see what was going on when we did a particular database modification. We update this script manually (do not use the SQL automatic scripting function!) so wa can keep a good control over where items are done and also the naming system is under control. /Bo -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf Of Siegfried Heintze Sent: den 19 oktober 2004 07:04 To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: [cvsnt] Synchronize source code with database? I'm using perl and a Microsoft Access Database to implement a web site. (Not my choice -- but it pays the bills). I just added some new columns to the 10MB database. Now I'm using CVSNT to store the perl code but not the Microsoft access database. Should I add the Microsoft Access database to the repository? Since we don't have any customers yet, there is not much interesting in the database except the metadata. I really don't want to store a new copy of the Microsoft Access database every time I commit. If I add the database with the -kb option, will it store a new copy of the database every time I commit the sandbox (assuming the database has been modified -- which is extremely likely)? I believe so. This is a problem because if I ever change some field names or table names in the database and need to role back, I won't have an old copy of the database to match the code! Well, this problem is not unique to Microsoft Access. What do other folks do? Thanks, Siegfried _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs