MySQL, Access, ODBC, Replication

[Beda Christoph Hammerschmidt]

MySQL, Access, ODBC, Replication


Hello,

i have a central mysql database that is accesed by multiple clients
running MS Access with ODBC.
This works fine if Access has a permanent connection to mysql.

But now, i want MS Access to operate offline (e.g. on notebook in the
field).
I tried to create a local replica of the ODBC database, but the local
replica still requires an ODBC connection to the running mysql server.
I do not know why.


What is teh best way to realize synchronization between a local and an
odbc database using MS Access ?

Thanks in advance

Beda

[Daven Thrice]

Re: MySQL, Access, ODBC, Replication


"Beda Christoph Hammerschmidt" <bchammer@web.d e> wrote in message
news:c2950d74.0 412011417.3c5c5 f0a@posting.goo gle.com...[color=blue]
> MySQL, Access, ODBC, Replication
>
>
> Hello,
>
> i have a central mysql database that is accesed by multiple clients
> running MS Access with ODBC.
> This works fine if Access has a permanent connection to mysql.
>
> But now, i want MS Access to operate offline (e.g. on notebook in the
> field).
> I tried to create a local replica of the ODBC database, but the local
> replica still requires an ODBC connection to the running mysql server.
> I do not know why.
>
>
> What is teh best way to realize synchronization between a local and an
> odbc database using MS Access ?[/color]

Are you using MyODBC or what?

I don't know how replication is now-days, but when it first came out, it
really sucked. I have pretty much stayed away from it as much as possible.

As I remember, though, you can setup a chain of database to replicate. Maybe
something like an in-between database would work. You sync the in between
database w/ the server, and then sync the laptop with the in between mdb.
Make sense?

Otherwise, jeez, what a mess. Where do you find support for something like
this? There are quite a few articles at mysql.org regarding Access, but I
don't recall seeing anything in regards to replication (although I've never
search for that key word).

I want to point out that just because you have an Access front end and are
working on a disconnected computer, doesn't mean that you have to limit
yourself to an Access .mdb file. I have MyODBC installed on my laptop, and I
am able to use local databases directly off my hard drive, with no
connection to a server or the Internet. The point is that MySQL has
replication capabilities. Rather than trying to sync an mdb with a mysql
database, consider going to MySQL on the laptop, as well. (If you can't beat
'em, join 'em).

Here, check this out:

http://www.mysql.com/search/?q=replication&charset=iso-8859-1

This group is mainly microsoft centered. There are a number of MySql
oriented newsgroups, such as alt.php.sql. Don't forget those resources if
you don't find an answer to your question here.

Daven

[David W. Fenton]

Re: MySQL, Access, ODBC, Replication

bchammer@web.de (Beda Christoph Hammerschmidt) wrote in
news:c2950d74.0 412011417.3c5c5 f0a@posting.goo gle.com:
[color=blue]
> MySQL, Access, ODBC, Replication
>
> i have a central mysql database that is accesed by multiple
> clients running MS Access with ODBC.
> This works fine if Access has a permanent connection to mysql.
>
> But now, i want MS Access to operate offline (e.g. on notebook in
> the field).
> I tried to create a local replica of the ODBC database, but the
> local replica still requires an ODBC connection to the running
> mysql server. I do not know why.
>
> What is teh best way to realize synchronization between a local
> and an odbc database using MS Access ?[/color]

Don't you think this is not an Access question at all, but a MySQL
question?

Or are you trying to use *Access* (i.e., *Jet*) replication of the
front end to accomplish this? That would explain why you still
needed a connection to the ODBC back end, since the front end
replica would not replicate the data, just the front end (and would
be identical to the original).

I have several clients with laptops using MDBs to store their data,
and what I've found works best is to have two front ends on the
laptop, one that connects to the shared data file, and one that
connects to a replica that is local to the laptop.

Another alternative that I use with one client (who hardly ever
usese the laptop connected to the network) is to have the laptop
edit *only* a replica, and then synch regularly with the main data
file when connected to the network.

This architecture ought to be the same for any replicated back end.

But, again, your question is a back end question, and belongs in a
MySQL newsgroup.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc