> -----Original Message-----
> From: Mark Stringham [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 22, 2002 2:51 PM
> To: Chuck Roberts
> Cc: Mysql; Mark Stringham
> Subject: RE: MySQL, MyODBC and MS Access
>
>
> Chuck -
> I am looking for a way for both MS access and MySQL to
> share realtime
> data so that if someone where to insert (through a web
> based admin)
> or update table in a MySQL db you could open your
> Access db and see
> the same data. I don't know if it is possible but that
> way there
> wouldn't be an export to MySQL procedure. Does that make sense?
>
> I don't know much about Myodbc except it allows you to
> export your
> Access database to MySQL. My question is if MySQL
> gets updated does
> Access get updated too?
>
> I have a client who wants everyone in the office to
> have the ability
> to update and view data in an Access db. My
> understanding of how
> access works is only one person can be connected or
> update the db
> at a time.(depending on the # of odbc connection you
Not true. Many people can be connected to an MDB file at the same
time if the MDB file is on a network drive. (I've done this.) But
Access only handles up to 10-15 simultaneous connections well.
Then you have the record locking problem too. What if someone
pulls up a record then forgets to "let go" of it? No one else can
update that record (though they could view it).
> have) My thought
> was if we got Access and MySQL talking, I could create
> a web based
You don't need to make it web-based.
> admin that would allow many folks to query and update
> the MySQL db
> and if MySQL and Access are talking then the data in
> the Access
> db would get updated as well. Really just trying to
> create a remote
> way to access and update from the Access db.
>
> Sorry for the long story but is this something you've
> done or is
> it not at all possible?
>
Yes this is possible. If you are going to have more than 10
simultaneous connections then I would go with Mysql backend with
an Access frontend (which requires ODBC). Otherwise I would just
plop an MDB file on a network drive. Everyone would be able to
see everyone else's changes in either case. You don't need to be
copying data between an Access MDB and a mysql db.
Does that make sense? It's easier than you think.
Chuck
p.s. We are working on the same thing here: an Access front end
for the pretty, user-friendly screens with a mysql backend db for
performance. BUT, myODBC allows Access front ends to come in from
the internet also, not just from another client on the company
network.
So, once a client is set up with Access and MyODBC, they can go
over the internet and update our mysql database.
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
