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
Received on Tue Jan 11 22:40:06 2005