Can I convert my .mdb file to a binary file for Subversion?

[Stapes]

Hi

I am trying to use TortoiseSVN Source Control on my Microsoft Access
databases, but it only works on binary files. Does anyone know how I
can m\ke my .mdb files into binary?

I tried looking at the Microsoft products, Visual Source Safe etc, but
to be honest, their website is a maze and I cannot find a version to
download anywhere.

Stapes

 

[Albert D. Kallal]

ms-access does work with Microsoft's Visual Source safe control system.

As for converting to binary? why? Do you convert your c++ code into binary
to make it source safe compatible?? (this is just nonsense).

If TortoiseSVN supports the standard interface that MS uses for their
development tools, then it is possible that it will work with ms-access. It
not ms-access you going to have to change here, your simply going to have to
choose a product that is compatible with visual source safe (which ms-access
supports, and most MS IDE's support), or your going have to use a product
that is designed to work with ms-access.

I only used source code control with VSS 6.0 and access 2003. You have to
download the source code ad-in for ms-access

Info link

http://support.microsoft.com/kb/837136/en-us


source code control for access Download page:
http://www.microsoft.com/downloads/...f4-a916-48c5-8f84-44b91fa774bc&displaylang=en


http://msdn.microsoft.com/office/understanding/access/

Just as a note, all of the above works because any object in ms-access can
be exported as a standard "text" document, and it is these "text" documents
that are placed in Visual Source safe. Thus, you can check in/out forms,
reports, code modes etc. You can even check in/out sql queries. So, using
VSS with ms-access not only allows source code and version control, but you
also allow more then one person to develop, and work on the application at
the same time. The "mdb" file is really only an container of objects, and
the whole processes of exporting modules, forms "in" and "out" of the source
safe is not any different then you pulling in and out "text" docuemtns of
c++ code etc that would occur in any other development platform. The above
VSS add-in allows you to continue to work in ms-access, and you simply asked
to check in/out objects as you use them. The "source safe" can then be used
to biuld a mdb based on these changes. You will of couse then create a mde
for your users (but, you likey been doing that with your mdb setup now
anyway).


Do note, it is assumed you split your database into an application part, and
a data part. I explain the concept of splitting here, and you need to be
"comfortable" with this concept before you adopt VSS

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

Note that you don't *have* to split, but it kind silly to develop an
application with the data mixed in with the code....and during the
development process you would NOT be able to have a production version in
use by your users....so, splitting is kind a must do for the development
processes.

 

[david]

Your MDB is a binary file.
You may wish to configure Subversion to recognise .mdb files as binary,
if it does not do so already.

To convert an MDB to a set of text files, use SaveAsText (google for
examples)
Text files are good for doing version comparisons, binary files are bad for
doing version comparisons.


You can't download Visual Source Safe, you have to buy it. (It
is included with some of the development tools).

If you have VSS, it can automate the process of converting the
binary file to a set of text files, but it isn't very good at it. We ended
up just using the binary mdb file.

(david)

 

[Stapes]

Your MDB is a binary file.
You may wish to configure Subversion to recognise .mdb files as binary,
if it does not do so already.

To convert an MDB to a set of text files, use SaveAsText (google for
examples)
Text files are good for doing version comparisons, binary files are bad for
doing version comparisons.

You can't download Visual Source Safe, you have to buy it. (It
is included with some of the development tools).

If you have VSS, it can automate the process of converting the
binary file to a set of text files, but it isn't very good at it. We ended
up just using the binary mdb file.

(david)









- Show quoted text -

I took your advice, and used these SaveAsText procedures. I found
this:

http://www.access-programmers.co.uk/forums/archive/index.php/t-99179.html

It is a function to Export all database objects to text files. This is
great. I can use Subversion on these files. However, I would like my
code to be exported in English. Is that possible?

And what should be in the Container called 'Scripts'. I had hoped that
would be my code, but it isn't. In fact, there is nothing in my
'Scripts' container.

Sta[es

 

[Stapes]

Your MDB is a binary file.
You may wish to configure Subversion to recognise .mdb files as binary,
if it does not do so already.

To convert an MDB to a set of text files, use SaveAsText (google for
examples)
Text files are good for doing version comparisons, binary files are bad for
doing version comparisons.

You can't download Visual Source Safe, you have to buy it. (It
is included with some of the development tools).

If you have VSS, it can automate the process of converting the
binary file to a set of text files, but it isn't very good at it. We ended
up just using the binary mdb file.

- Show quoted text -

I took your advice, and used these SaveAsText procedures. I found
this:

http://www.access-programmers.co.uk/forums/archive/index.php/t-99179....

It is a function to Export all database objects to text files. This is
great. I can use Subversion on these files. However, I would like my
code to be exported in English. Is that possible?

And what should be in the Container called 'Scripts'. I had hoped that
would be my code, but it isn't. In fact, there is nothing in my
'Scripts' container.

Sta[es- Hide quoted text -

- Show quoted text -

Forget that last question - I found the code.