Python & Remote Access Database
drs at ecp.cc
Fri Apr 11 07:34:44 CEST 2003
"Dennis Lee Bieber" <wlfraed at ix.netcom.com> wrote in message
news:7enhm-os2.ln1 at beastie.ix.netcom.com...
> mat fed this fish to the penguins on Thursday 10 April 2003 04:51 am:
> >> Assuming that by access you mean MS Access, I think there are 3
> >> solutions. The real problem is that Access is not a db server, so
> >> using it remotely, even in an all windows environment, is not a
> >> simple thing (or at least not a good thing).
> Access (actually JET -- Access is more of a GUI front-end to JET)
> described as something like "file server RDBM"; all the processing is
> normally done by running the JET engine on the local machine, and
> copying the .MDB file(s) across the network as needed. Of course, JET
> only runs on M$ Windows (as a DLL) so you can't get it from a Linux
Generally this is correct, but wrapping calls to Access/Jet in a remote
object keeps the processing remote. Thus using pyro should allow a local
process on linux to manipulate an object on windows which would remotely
interacted with an access db. As I said, it is neither a simple nor a good
way to proceed, but it should work in a pinch.
More information about the Python-list