MyODBC

------=_NextPart_000_0010_01C58D72.BD8BEFA0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I am considering using MyODBC to connect to a MySQL database on a web =
server from a desktop application developed using Access 2002.

=20

My desktop application is deployed as a complete package including =
Access Runtime files.

=20

I am currently looking at enhancing the application to include access to =
a MYSQL database on a web server and have a number of questions =
regarding the use of MyODBC:

1. What additional dlls would I need to include in the installation =
package to allow my application to connect to a MYSQL database? Ie. Do =
I need to include a copy of MySQL and/or MyODBC only on all client PCs =
running my software?

2. If I am using MyODBC solely to connect to a MYSQL database on a =
webserver then do I need a license for MyODBC? My clients are licensed =
to use my product but do not have the right to the source code. =20

=20

Any feedback on the above items will be most appreciated.



C. Rose


------=_NextPart_000_0010_01C58D72.BD8BEFA0--

RE: MyODBC

You will need MyODBC installed on each client PC, but as it is open =
source
software, this is not an issue. It can be freely downloaded from the =
MySQL
website. If you do decide to distribute the MyODBC bianries with your
application, then you should also distribute the MyODBC source (but you =
do
not need to distribute your own source).

You only need one instance of MySQL, installed on the database server
machine.

In my experience, the biggest issue you will face regards Access linked
tables. When using Access with MyODBC (or any other ODBC data source =
for
that matter), you will almost certainly use Access linked tables (and
possibly passthrough queries). The implementation issue you have is =
that if
you change the definition of the ODBC datasource (e.g. server name, =
database
name, userid, password, etc), Access seems to require the linked tables =
to
be refreshed using the linked table manager. In your scenario, this =
will
require the linked table manager to be available ON YOUR CLIENT'S SITE -
i.e. you will not simply be able to package and distribute your =
application
as you do now. If anyone knows a way around this requirement to refresh =
the
linked tables, I'd be very interested to hear.......

Martin

-----Original Message-----
From: Christine Rose [mailto:cxrose1@yahoo.co.nz]=20
Sent: 20 July 2005 10:34
To: myodbc@lists.mysql.com
Subject: MyODBC


I am considering using MyODBC to connect to a MySQL database on a web =
server
from a desktop application developed using Access 2002.

=20

My desktop application is deployed as a complete package including =
Access
Runtime files.

=20

I am currently looking at enhancing the application to include access to =
a
MYSQL database on a web server and have a number of questions regarding =
the
use of MyODBC:

1. What additional dlls would I need to include in the installation
package to allow my application to connect to a MYSQL database? Ie. Do =
I
need to include a copy of MySQL and/or MyODBC only on all client PCs =
running
my software?

2. If I am using MyODBC solely to connect to a MYSQL database on a
webserver then do I need a license for MyODBC? My clients are licensed =
to
use my product but do not have the right to the source code. =20

=20

Any feedback on the above items will be most appreciated.



C. Rose



--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc@m.gmane.o rg