Version control with CVSNT or VSS

[Siegfried Heintze]

I'm using Microsoft Access and for my web site. I have a lot of perl code
that manipulates the database on behalf of the user.

What happens if I add the Microsoft Access database to a Visual Source Safe
(VSS) repository? Does VSS only store the deltas between access database
files? If so, maybe I should abandon CVSNT in favor of VSS. If not, that is
a lot of wasted disk space.

Let assume, however, that I am stuck with CVSNT which does not store deltas
for non-text files. If I roll back the source code to an earlier version,
that code may not match my latest copy of my access database!

What options do I have for keeping my source code synchronized with my
database? I suppose I could extract the entire database as XML code and then
CVSNT could only store the deltas.

How might I automate the process of extracting the XML code to a text file
so I could alter created the Microsoft Access database?

What other options are there? Can I extract the DDL and use that to create
the database? SQL Server has this feature -- you can even include the
contents with a massive number of insert statements. Is there a similar
feature in Access?

What are other folks doing to store Access databases in version control?

Thanks,
Siegfried