Take a look at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnacc2k2/ht
ml/odc_accessxml.asp for tips on exporting to XML from Access 2002 using
VBA. BTW, Access 2003 has even more support for XML. I have a simple VBA
script that will export objects from an Access database to xml/xls files.
Basic but effective. Thus, I can version the human-readable files. So far,
I can only figure out how to export Tables and Queries to xml/xsl.
Nick Seigal
-----Original Message-----
From: andy@brummerfamily.com [mailto:andy@brummerfamily.com]
Sent: Tuesday, January 11, 2005 2:07 PM
To: users@subversion.tigris.org
Subject: Re: Can u use it with Access?
Quoting Shawn Harrison <harrison@tbc.net>:
> Peter Valdemar Mørch wrote [01/11/05 2:44 PM]:
>> Steven H @ orcon wrote:
>>
>>> So basically your wanting a way to manage all the vba source code
>>> behind your access application?
>>>
>>> The only real achievable way of doing this would be to somehow
>>> 'export' the source from access (copy & paste into text files) and
>>> have SVN manage those exported files.
>>
>>
>> Yikes! Cut'n'paste... Glad I'm not using Access!
>> Yes, I don't know #"€)(/% about Access...
>>
>
> Well, it's not quite that bad, but almost. You can export the files in
> the file menu in MS Office applications, but yes, all the code is kept
> in binary (though not compiled) form in the database / Word template /
> Excel file / whatever. Pain in the rear.
>
> Subversion is almost useless for this, because you can never directly
> do a diff. If you want to compare the code in two versions of a MS
> Office file, you have to export from both of them.
>
> My work-around: I've got VBA scripts to export all the source from a
> given MS Office file, to a src directory. Then I can version that, and
> do diffs to see what's changed. Still a pain in the rear, but AFAIK
> it's the best you can do on that platform.
>
> A better solution: Get a different work platform if at all possible.
> Much better to work in Python, for a host of reasons, if you can. For
> that matter, much better to use PostgreSQL, for a host of similar
> reasons, if you can. But I'm getting WAY off topic.... (my LAMP =
> Linux Apache mod_python PostgreSQL).
>
> I guess the connection is that some people are in a Windows shop (the
> tools, not just the OS), for any number of reasons, but they still
> need to find a way to make use of version control. I guess there's a
> niche business market for someone....
>
> --
> ________________
> harrison@tbc.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
Does the latest version of Access have a save as XML file like Word and
Excel have? In that case you could store the XML file in Subversion, after
removing all the non-application level data from data database of course.
It wouldn't be as clean as using seperate files, but it would work better
then versioning the binary files.
-Andy Brummer
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 12 03:42:46 2005