Use the undocumented SaveAsText & LoadFromText methods to save/load
various objects as/from text files. (But those methods ARE NOT
officially documented, so I guess that they could disappear at any
time.) Run them via automation from any automation-capable client; eg.
another (central) Access database.
So, you could start the central database, select a different database
& object from suitable dropdown lists, hit a "book in" button, & the
code would retrieve the relevant text file from your Unix server, then
programatically open the relevant database & run the LoadFromText (all
from automation).
I haven't done that myself, but I don't see why it shouldn't work.
HTH,
TC
x25ugip1@freenet.de (Marco Stolpe) wrote in message news:<65d35fc1.0402020743.5edcdfd6@posting.google. com>...[color=blue]
> Hi,
>
> I'm working on a medium size Access database together with another
> developer. We're using Visual Basic to provide some extended
> functionality to our users. After I read some books about managing
> several issues regarding implementation (coding standards, version
> control, self-written code checkers, etc.), I'm wondering how to apply
> such knowledge and techniques to our own project.
>
> What I would like to do is to manage my VBA source code with CVS on a
> Unix machine in the form of simple text files. I'd like to edit them
> with an arbitrary text editor (probably Emacs). This would allow me -
> for example - to write code-checkers, code-generators (maybe
> generating functionality from a specification in XML), documentation
> generators and so on in any scripting language I like (probably Perl).
> In other words, I'd like to flee the built in Access IDE.
>
> The only remaining question is how to get text source files imported
> into Access - if possible without any user interaction (that is: from
> a script or C/C++ command line application, whatever).
>
> Does anyone know how to do this?
>
> Thanks in advance for any replies,
>
> Marco[/color]