MyODBC

Hi,

Does ASP work with MyODBC?

I tried to connect to MySQL using connection string "Driver={mySQL};
Server=localhost; Port=3306; Option=0; Socket=; Stmt=; Database=myDB; Uid=;
Pwd=" and I get this message "Data source name not found and no default
driver specified "


Regards,

Eng Wah



------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/products/myodbc/manual_toc.html (the manual)
http://lists.mysql.com/ (the list archive)

To unsubscribe, e-mail
To unsubscribe from Yahoo! Groups version, e-mail myodbc-unsubscribe@yahoogroups.com

RE: MyODBC

Sure does..
DSN=MYDSN;User Id=username;PASSWORD=password;DESC=MySQL ODBC 3.51 Driver
DSN;DATABASE=dbname;SERVER=servername;UID=username;PORT=3306 ;OPTION=3;STMT=;

works for me
which version of odbc are you using, the DESC would be different for 2.5
Alan

> -----Original Message-----
> From: engwah@powersys.com.my [mailto:engwah@powersys.com.my]
> Sent: Monday, 11 November 2002 18:43
> To: myodbc@lists.mysql.com
> Subject: MyODBC
>
>
> Hi,
>
> Does ASP work with MyODBC?
>
> I tried to connect to MySQL using connection string "Driver={mySQL};
> Server=localhost; Port=3306; Option=0; Socket=; Stmt=;
> Database=myDB; Uid=;
> Pwd=" and I get this message "Data source name not found and no default
> driver specified "
>
>
> Regards,
>
> Eng Wah
>
>
>
> ------------------------------------------------------------ ---------
> Before posting, please check:
> http://www.mysql.com/products/myodbc/manual_toc.html (the manual)
> http://lists.mysql.com/ (the list archive)
>
> To unsubscribe, e-mail
> To unsubscribe from Yahoo! Groups version, e-mail
> myodbc-unsubscribe@yahoogroups.com
>



------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/products/myodbc/manual_toc.html (the manual)
http://lists.mysql.com/ (the list archive)

To unsubscribe, e-mail
To unsubscribe from Yahoo! Groups version, e-mail myodbc-unsubscribe@yahoogroups.com

Re: MyODBC

Hi

Have a look at http://www.dwam.net/mysql/

You can find there examples and tips for using ASP with MySQL via =
MyODBC.

/////////// D W A M =
////////////////////////////////////////////////////
Guillaume de Lafontaine - webmaster@dwam.com
> NT Docs & Ressources : http://www.dwam.net/
> Services Internet : http://www.w3space.com/
> Annuaire Aquitaine : http://www.aquitanet.com/
> Espace TeleTravail : http://www.w3workers.com/
=20
-----Message d'origine-----
De : engwah@powersys.com.my
=C0 : myodbc@lists.mysql.com
Date : lundi 11 novembre 2002 08:37
Objet : MyODBC


|Hi,
|
|Does ASP work with MyODBC?
|
|I tried to connect to MySQL using connection string "Driver=3D{mySQL};
|Server=3Dlocalhost; Port=3D3306; Option=3D0; Socket=3D; Stmt=3D; =
Database=3DmyDB; Uid=3D;
|Pwd=3D" and I get this message "Data source name not found and no =
default
|driver specified "
|
|
|Regards,
|
|Eng Wah
|
|
|
|----------------------------------------------------------- ----------
|Before posting, please check:
| http://www.mysql.com/products/myodbc/manual_toc.html (the manual)
| http://lists.mysql.com/ (the list archive)
|
|To unsubscribe, e-mail
|To unsubscribe from Yahoo! Groups version, e-mail =
myodbc-unsubscribe@yahoogroups.com
|


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/products/myodbc/manual_toc.html (the manual)
http://lists.mysql.com/ (the list archive)

To unsubscribe, e-mail
To unsubscribe from Yahoo! Groups version, e-mail myodbc-unsubscribe@yahoogroups.com

RE: MyODBC

Can you ping the host OK? I presume the server and MySQL are running?

-----Original Message-----
From: Tim McCoy [mailto:tmccoy@3peaks.net]
Sent: Friday, 16 May 2003 6:34 PM
To: myodbc@lists.mysql.com
Subject: MyODBC


MYSQL is new to me, so sorry if this question has been asked before.

I am trying to connect through MyODBC but keep getting the same error
message "Can't connect to MySQL server on (10060)". Although I
have managed to connect using other machines with the same settings. The
only way I can reproduce the error message on a machine which can
connect is by changing the default port number. Is there a second port
number that MyODBC uses if the default 3306 is in use?

Tim.

TIME-XS
3Peaks Solutions
01925 752212


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

RE: MYODBC

Yes, mine says that too. I just ignore it and things work OK. After a
default install you need to log in as root with an empty password to get
access.

All the issues about installing (before, after, during) are well covered
in the MySQL manual chapter 2. See section 2.2.1 in particular for
Windows details. The archives of this mailing list cover most of it
again too.

John Bonnett

-----Original Message-----
From: Ron Jones [mailto:Ron.Jones@thecopiousgroup.com]=20
Sent: Saturday, 16 October 2004 9:45 PM
To: myodbc@lists.mysql.com
Subject: MYODBC


I have been attempting to install MySQL for some time now with no
success. In the winmysqladmin window, myodbc shows file 3.51 driver is
not found. How is this negatively impacting my ability to install
correctly.

Is this causing all my access and/or privileges to be denied?

Thank you for your insight and foresight,

Ron Jones
216.691.1103
www.thecopiousgroup.com=20



--
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

RE: myodbc

This is the sort of setup that I use. What problem did you have with
configuring ODBC; I presume you mean creating a DSN?

You will also need to make sure that the MySQL server running on Linux
allows you to make a connection from your Windows machine. You may need =
an
appropriate GRANT for whatever user name you are using when connecting =
from
Windows.

John Bonnett

-----Original Message-----
From: fatih "gönüllü [mailto:fgonullu2002@yahoo.com]=20
Sent: Thursday, 24 February 2005 11:50 PM
To: myodbc@lists.mysql.com
Subject: myodbc

hi:) i established mysql under linux system and runing without =
problem. i
want to control with windows by a program wroten delphi. i setup myodbc
under windows but i couldn't configure it. i have no idea. there is BDE
Administaror in windows.
if you can help me, i m very happy.


__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around=20
http://mail.yahoo.com=20

--
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

RE: MyODBC

=20
Below is explanation and a sample code to refresh linked table, taking
from MS-Access help on "Refresh Link" method

==================== =====3D=
==================== =====3D=
==================== ==
==================== =====3D=
==================== =====3D=
==================== ==
RefreshLink Method
=20

Updates the connection information for a linked table (Microsoft Jet
workspaces only).

Syntax

tabledef.RefreshLink

The tabledef placeholder specifies the TableDef object representing the
linked table whose connection information you want to update.

Remarks

To change the connection information for a linked table, reset the
Connect property of the corresponding TableDef object and then use the
RefreshLink method to update the information. Using RefreshLink method
doesn't change the linked table's properties and Relation objects.

For this connection information to exist in all collections associated
with the TableDef object that represents the linked table, you must use
the Refresh method on each collection.

==================== =====3D=
==================== =====3D=
==================== ==
==================== =====3D=
==================== =====3D=
===================3D

RefreshLink Method Example

This example uses the RefreshLink method to refresh the data in a linked
table after its connection has been changed from one data source to
another. The RefreshLinkOutput procedure is required for this procedure
to run.

Sub RefreshLinkX()

Dim dbsCurrent As Database
Dim tdfLinked As TableDef

' Open a database to which a linked table can be
' appended.
Set dbsCurrent =3D OpenDatabase("DB1.mdb")

' Create a linked table that points to a Microsoft=20
' SQL Server database.
Set tdfLinked =3D _
dbsCurrent.CreateTableDef("AuthorsTable")
=20
' Note: The DSN referenced below must be configured to=20
' use Microsoft Windows NT Authentication Mode to=20
' authorize user access to the Microsoft SQL Server.
tdfLinked.Connect =3D _
"ODBC;DATABASE=3Dpubs;DSN=3DPublishers"
tdfLinked.SourceTableName =3D "authors"
dbsCurrent.TableDefs.Append tdfLinked

' Display contents of linked table.
Debug.Print _
"Data from linked table connected to first source:"
RefreshLinkOutput dbsCurrent

' Change connection information for linked table and=20
' refresh the connection in order to make the new data=20
' available.
=20
' Note: The DSN referenced below must be configured to=20
' use Microsoft Windows NT Authentication Mode to=20
' authorize user access to the Microsoft SQL Server.
tdfLinked.Connect =3D _
"ODBC;DATABASE=3Dpubs;DSN=3DNewPublishers"
tdfLinked.RefreshLink

' Display contents of linked table.
Debug.Print _
"Data from linked table connected to second source:"
RefreshLinkOutput dbsCurrent

' Delete linked table because this is a demonstration.
dbsCurrent.TableDefs.Delete tdfLinked.Name

dbsCurrent.Close

End Sub

Sub RefreshLinkOutput(dbsTemp As Database)

Dim rstRemote As Recordset
Dim intCount As Integer

' Open linked table.
Set rstRemote =3D _
dbsTemp.OpenRecordset("AuthorsTable")

intCount =3D 0

' Enumerate Recordset object, but stop at 50 records.
With rstRemote
Do While Not .EOF And intCount < 50
Debug.Print , .Fields(0), .Fields(1)
intCount =3D intCount + 1
.MoveNext
Loop
If Not .EOF Then Debug.Print , "[more records]"
.Close
End With

End Sub


Mikhail Berman

-----Original Message-----
From: Martin King-Turner [mailto:martin.kt@nb2bc.co.uk]=20
Sent: Wednesday, July 20, 2005 10:27 AM
To: 'Christine Rose'; myodbc@lists.mysql.com
Subject: 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]
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



--=20
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:
http://lists.mysql.com/myodbc?unsub=3Dmberman@ivesinc.com


--
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

Re: MyODBC

Not an Attorney, but I think if you have "closed source" app
distributed with Mysql, you need a license. Maybe I am reading wrong,
but here's some links:

http://www.mysql.com/company/legal/licensing/index.html
http://www.mysql.com/company/legal/licensing/opensource-lice nse.html

About the dll's, I dont know what is entailed, I bet you could hunt
down the dll's and script it into your app installer somehow.

Greg

On 7/20/05, Berman, Mikhail wrote:
>=20
> Below is explanation and a sample code to refresh linked table, taking
> from MS-Access help on "Refresh Link" method
>=20
> ==================== =====
==================== =====3D=
==================== ===3D
> ==================== =====
==================== =====3D=
==================== ===3D
> RefreshLink Method
>=20
>=20
> Updates the connection information for a linked table (Microsoft Jet
> workspaces only).
>=20
> Syntax
>=20
> tabledef.RefreshLink
>=20
> The tabledef placeholder specifies the TableDef object representing the
> linked table whose connection information you want to update.
>=20
> Remarks
>=20
> To change the connection information for a linked table, reset the
> Connect property of the corresponding TableDef object and then use the
> RefreshLink method to update the information. Using RefreshLink method
> doesn't change the linked table's properties and Relation objects.
>=20
> For this connection information to exist in all collections associated
> with the TableDef object that represents the linked table, you must use
> the Refresh method on each collection.
>=20
> ==================== =====
==================== =====3D=
==================== ===3D
> ==================== =====
==================== =====3D=
====================
>=20
> RefreshLink Method Example
>=20
> This example uses the RefreshLink method to refresh the data in a linked
> table after its connection has been changed from one data source to
> another. The RefreshLinkOutput procedure is required for this procedure
> to run.
>=20
> Sub RefreshLinkX()
>=20
> Dim dbsCurrent As Database
> Dim tdfLinked As TableDef
>=20
> ' Open a database to which a linked table can be
> ' appended.
> Set dbsCurrent =3D OpenDatabase("DB1.mdb")
>=20
> ' Create a linked table that points to a Microsoft
> ' SQL Server database.
> Set tdfLinked =3D _
> dbsCurrent.CreateTableDef("AuthorsTable")
>=20
> ' Note: The DSN referenced below must be configured to
> ' use Microsoft Windows NT Authentication Mode to
> ' authorize user access to the Microsoft SQL Server.
> tdfLinked.Connect =3D _
> "ODBC;DATABASE=3Dpubs;DSN=3DPublishers"
> tdfLinked.SourceTableName =3D "authors"
> dbsCurrent.TableDefs.Append tdfLinked
>=20
> ' Display contents of linked table.
> Debug.Print _
> "Data from linked table connected to first source:"
> RefreshLinkOutput dbsCurrent
>=20
> ' Change connection information for linked table and
> ' refresh the connection in order to make the new data
> ' available.
>=20
> ' Note: The DSN referenced below must be configured to
> ' use Microsoft Windows NT Authentication Mode to
> ' authorize user access to the Microsoft SQL Server.
> tdfLinked.Connect =3D _
> "ODBC;DATABASE=3Dpubs;DSN=3DNewPublishers"
> tdfLinked.RefreshLink
>=20
> ' Display contents of linked table.
> Debug.Print _
> "Data from linked table connected to second source:"
> RefreshLinkOutput dbsCurrent
>=20
> ' Delete linked table because this is a demonstration.
> dbsCurrent.TableDefs.Delete tdfLinked.Name
>=20
> dbsCurrent.Close
>=20
> End Sub
>=20
> Sub RefreshLinkOutput(dbsTemp As Database)
>=20
> Dim rstRemote As Recordset
> Dim intCount As Integer
>=20
> ' Open linked table.
> Set rstRemote =3D _
> dbsTemp.OpenRecordset("AuthorsTable")
>=20
> intCount =3D 0
>=20
> ' Enumerate Recordset object, but stop at 50 records.
> With rstRemote
> Do While Not .EOF And intCount < 50
> Debug.Print , .Fields(0), .Fields(1)
> intCount =3D intCount + 1
> .MoveNext
> Loop
> If Not .EOF Then Debug.Print , "[more records]"
> .Close
> End With
>=20
> End Sub
>=20
>=20
> Mikhail Berman
>=20
> -----Original Message-----
> From: Martin King-Turner [mailto:martin.kt@nb2bc.co.uk]
> Sent: Wednesday, July 20, 2005 10:27 AM
> To: 'Christine Rose'; myodbc@lists.mysql.com
> Subject: RE: MyODBC
>=20
> 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).
>=20
> You only need one instance of MySQL, installed on the database server
> machine.
>=20
> 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.......
>=20
> Martin
>=20
> -----Original Message-----
> From: Christine Rose [mailto:cxrose1@yahoo.co.nz]
> Sent: 20 July 2005 10:34
> To: myodbc@lists.mysql.com
> Subject: MyODBC
>=20
>=20
> I am considering using MyODBC to connect to a MySQL database on a web
> server
> from a desktop application developed using Access 2002.
>=20
>=20
>=20
> My desktop application is deployed as a complete package including
> Access
> Runtime files.
>=20
>=20
>=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:
>=20
> 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?
>=20
> 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
>=20
> Any feedback on the above items will be most appreciated.
>=20
>=20
>=20
> C. Rose
>=20
>=20
>=20
> --
> MySQL ODBC Mailing List
> For list archives: http://lists.mysql.com/myodbc
> To unsubscribe:
> http://lists.mysql.com/myodbc?unsub=3Dmberman@ivesinc.com
>=20
>=20
> --
> MySQL ODBC Mailing List
> For list archives: http://lists.mysql.com/myodbc
> To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dretheoff@gmail.c=
om
>=20
>=20


--=20
Greg Fischer
1st Byte Solutions
http://www.1stbyte.com

--
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

RE: MyODBC

Simplest and safest way to avoid any issues is to not distribute MySQL or
MyODBC with your Access app. They're freely downloadable from mysql.com
anyway, so there's really no need to re-distribute them.

-----Original Message-----
From: Greg Fischer [mailto:retheoff@gmail.com]
Sent: 21 July 2005 17:23
To: myodbc@lists.mysql.com; Christine Rose
Subject: Re: MyODBC


Not an Attorney, but I think if you have "closed source" app distributed
with Mysql, you need a license. Maybe I am reading wrong, but here's some
links:

http://www.mysql.com/company/legal/licensing/index.html
http://www.mysql.com/company/legal/licensing/opensource-lice nse.html

About the dll's, I dont know what is entailed, I bet you could hunt down the
dll's and script it into your app installer somehow.

Greg

On 7/20/05, Berman, Mikhail wrote:
>
> Below is explanation and a sample code to refresh linked table, taking
> from MS-Access help on "Refresh Link" method
>
> ============================================================ ==========
> ==
> ============================================================ ============
> RefreshLink Method
>
>
> Updates the connection information for a linked table (Microsoft Jet
> workspaces only).
>
> Syntax
>
> tabledef.RefreshLink
>
> The tabledef placeholder specifies the TableDef object representing
> the linked table whose connection information you want to update.
>
> Remarks
>
> To change the connection information for a linked table, reset the
> Connect property of the corresponding TableDef object and then use the
> RefreshLink method to update the information. Using RefreshLink method
> doesn't change the linked table's properties and Relation objects.
>
> For this connection information to exist in all collections associated
> with the TableDef object that represents the linked table, you must
> use the Refresh method on each collection.
>
> ============================================================ ==========
> ==
> ============================================================ =========
>
> RefreshLink Method Example
>
> This example uses the RefreshLink method to refresh the data in a
> linked table after its connection has been changed from one data
> source to another. The RefreshLinkOutput procedure is required for
> this procedure to run.
>
> Sub RefreshLinkX()
>
> Dim dbsCurrent As Database
> Dim tdfLinked As TableDef
>
> ' Open a database to which a linked table can be
> ' appended.
> Set dbsCurrent = OpenDatabase("DB1.mdb")
>
> ' Create a linked table that points to a Microsoft
> ' SQL Server database.
> Set tdfLinked = _
> dbsCurrent.CreateTableDef("AuthorsTable")
>
> ' Note: The DSN referenced below must be configured to
> ' use Microsoft Windows NT Authentication Mode to
> ' authorize user access to the Microsoft SQL Server.
> tdfLinked.Connect = _
> "ODBC;DATABASE=pubs;DSN=Publishers"
> tdfLinked.SourceTableName = "authors"
> dbsCurrent.TableDefs.Append tdfLinked
>
> ' Display contents of linked table.
> Debug.Print _
> "Data from linked table connected to first source:"
> RefreshLinkOutput dbsCurrent
>
> ' Change connection information for linked table and
> ' refresh the connection in order to make the new data
> ' available.
>
> ' Note: The DSN referenced below must be configured to
> ' use Microsoft Windows NT Authentication Mode to
> ' authorize user access to the Microsoft SQL Server.
> tdfLinked.Connect = _
> "ODBC;DATABASE=pubs;DSN=NewPublishers"
> tdfLinked.RefreshLink
>
> ' Display contents of linked table.
> Debug.Print _
> "Data from linked table connected to second source:"
> RefreshLinkOutput dbsCurrent
>
> ' Delete linked table because this is a demonstration.
> dbsCurrent.TableDefs.Delete tdfLinked.Name
>
> dbsCurrent.Close
>
> End Sub
>
> Sub RefreshLinkOutput(dbsTemp As Database)
>
> Dim rstRemote As Recordset
> Dim intCount As Integer
>
> ' Open linked table.
> Set rstRemote = _
> dbsTemp.OpenRecordset("AuthorsTable")
>
> intCount = 0
>
> ' Enumerate Recordset object, but stop at 50 records.
> With rstRemote
> Do While Not .EOF And intCount < 50
> Debug.Print , .Fields(0), .Fields(1)
> intCount = intCount + 1
> .MoveNext
> Loop
> If Not .EOF Then Debug.Print , "[more records]"
> .Close
> End With
>
> End Sub
>
>
> Mikhail Berman
>
> -----Original Message-----
> From: Martin King-Turner [mailto:martin.kt@nb2bc.co.uk]
> Sent: Wednesday, July 20, 2005 10:27 AM
> To: 'Christine Rose'; myodbc@lists.mysql.com
> Subject: 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]
> 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.
>
>
>
> My desktop application is deployed as a complete package including
> Access Runtime files.
>
>
>
> 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.
>
>
>
> 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=mberman@ivesinc.com
>
>
> --
> MySQL ODBC Mailing List
> For list archives: http://lists.mysql.com/myodbc
> To unsubscribe: http://lists.mysql.com/myodbc?unsub=retheoff@gmail.com
>
>


--
Greg Fischer
1st Byte Solutions
http://www.1stbyte.com

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=martin.kt@nb2bc.co.uk


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

RE: MyODBC

Dear Greg,

Microsoft produces "Microsoft Office Access2003 Developer Extensions" to
create legal run-time applications, that does not require MS-Access to
be installed on each client's PC.

Mikhail Berman

-----Original Message-----
From: Greg Fischer [mailto:retheoff@gmail.com]=20
Sent: Thursday, July 21, 2005 12:23 PM
To: myodbc@lists.mysql.com; Christine Rose
Subject: Re: MyODBC

Not an Attorney, but I think if you have "closed source" app distributed
with Mysql, you need a license. Maybe I am reading wrong, but here's
some links:

http://www.mysql.com/company/legal/licensing/index.html
http://www.mysql.com/company/legal/licensing/opensource-lice nse.html

About the dll's, I dont know what is entailed, I bet you could hunt down
the dll's and script it into your app installer somehow.

Greg

On 7/20/05, Berman, Mikhail wrote:
>=20
> Below is explanation and a sample code to refresh linked table, taking

> from MS-Access help on "Refresh Link" method
>=20
> =
==================== =====3D=
==================== =====3D=
====================
> ===20
> =
==================== =====3D=
==================== =====3D=
====================
> ==
> RefreshLink Method
>=20
>=20
> Updates the connection information for a linked table (Microsoft Jet=20
> workspaces only).
>=20
> Syntax
>=20
> tabledef.RefreshLink
>=20
> The tabledef placeholder specifies the TableDef object representing=20
> the linked table whose connection information you want to update.
>=20
> Remarks
>=20
> To change the connection information for a linked table, reset the=20
> Connect property of the corresponding TableDef object and then use the

> RefreshLink method to update the information. Using RefreshLink method

> doesn't change the linked table's properties and Relation objects.
>=20
> For this connection information to exist in all collections associated

> with the TableDef object that represents the linked table, you must=20
> use the Refresh method on each collection.
>=20
> =
==================== =====3D=
==================== =====3D=
====================
> ===20
> =
==================== =====3D=
==================== =====3D=
===================3D
>=20
> RefreshLink Method Example
>=20
> This example uses the RefreshLink method to refresh the data in a=20
> linked table after its connection has been changed from one data=20
> source to another. The RefreshLinkOutput procedure is required for=20
> this procedure to run.
>=20
> Sub RefreshLinkX()
>=20
> Dim dbsCurrent As Database
> Dim tdfLinked As TableDef
>=20
> ' Open a database to which a linked table can be
> ' appended.
> Set dbsCurrent =3D OpenDatabase("DB1.mdb")
>=20
> ' Create a linked table that points to a Microsoft
> ' SQL Server database.
> Set tdfLinked =3D _
> dbsCurrent.CreateTableDef("AuthorsTable")
>=20
> ' Note: The DSN referenced below must be configured to
> ' use Microsoft Windows NT Authentication Mode to
> ' authorize user access to the Microsoft SQL Server.
> tdfLinked.Connect =3D _
> "ODBC;DATABASE=3Dpubs;DSN=3DPublishers"
> tdfLinked.SourceTableName =3D "authors"
> dbsCurrent.TableDefs.Append tdfLinked
>=20
> ' Display contents of linked table.
> Debug.Print _
> "Data from linked table connected to first source:"
> RefreshLinkOutput dbsCurrent
>=20
> ' Change connection information for linked table and
> ' refresh the connection in order to make the new data
> ' available.
>=20
> ' Note: The DSN referenced below must be configured to
> ' use Microsoft Windows NT Authentication Mode to
> ' authorize user access to the Microsoft SQL Server.
> tdfLinked.Connect =3D _
> "ODBC;DATABASE=3Dpubs;DSN=3DNewPublishers"
> tdfLinked.RefreshLink
>=20
> ' Display contents of linked table.
> Debug.Print _
> "Data from linked table connected to second source:"
> RefreshLinkOutput dbsCurrent
>=20
> ' Delete linked table because this is a demonstration.
> dbsCurrent.TableDefs.Delete tdfLinked.Name
>=20
> dbsCurrent.Close
>=20
> End Sub
>=20
> Sub RefreshLinkOutput(dbsTemp As Database)
>=20
> Dim rstRemote As Recordset
> Dim intCount As Integer
>=20
> ' Open linked table.
> Set rstRemote =3D _
> dbsTemp.OpenRecordset("AuthorsTable")
>=20
> intCount =3D 0
>=20
> ' Enumerate Recordset object, but stop at 50 records.
> With rstRemote
> Do While Not .EOF And intCount < 50
> Debug.Print , .Fields(0), .Fields(1)
> intCount =3D intCount + 1
> .MoveNext
> Loop
> If Not .EOF Then Debug.Print , "[more records]"
> .Close
> End With
>=20
> End Sub
>=20
>=20
> Mikhail Berman
>=20
> -----Original Message-----
> From: Martin King-Turner [mailto:martin.kt@nb2bc.co.uk]
> Sent: Wednesday, July 20, 2005 10:27 AM
> To: 'Christine Rose'; myodbc@lists.mysql.com
> Subject: RE: MyODBC
>=20
> You will need MyODBC installed on each client PC, but as it is open=20
> source software, this is not an issue. It can be freely downloaded=20
> from the MySQL website. If you do decide to distribute the MyODBC=20
> bianries with your application, then you should also distribute the=20
> MyODBC source (but you do not need to distribute your own source).
>=20
> You only need one instance of MySQL, installed on the database server=20
> machine.
>=20
> In my experience, the biggest issue you will face regards Access=20
> linked tables. When using Access with MyODBC (or any other ODBC data=20
> source for that matter), you will almost certainly use Access linked=20
> tables (and possibly passthrough queries). The implementation issue=20
> you have is that if you change the definition of the ODBC datasource=20
> (e.g. server name, database name, userid, password, etc), Access seems

> to require the linked tables to be refreshed using the linked table=20
> 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=20
> able to package and distribute your application as you do now. If=20
> anyone knows a way around this requirement to refresh the linked=20
> tables, I'd be very interested to hear.......
>=20
> Martin
>=20
> -----Original Message-----
> From: Christine Rose [mailto:cxrose1@yahoo.co.nz]
> Sent: 20 July 2005 10:34
> To: myodbc@lists.mysql.com
> Subject: MyODBC
>=20
>=20
> I am considering using MyODBC to connect to a MySQL database on a web=20
> server from a desktop application developed using Access 2002.
>=20
>=20
>=20
> My desktop application is deployed as a complete package including=20
> Access Runtime files.
>=20
>=20
>=20
> I am currently looking at enhancing the application to include access=20
> to a MYSQL database on a web server and have a number of questions=20
> regarding the use of MyODBC:
>=20
> 1. What additional dlls would I need to include in the
installation
> package to allow my application to connect to a MYSQL database? Ie. =20
> Do I need to include a copy of MySQL and/or MyODBC only on all client=20
> PCs running my software?
>=20
> 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=20
> licensed to use my product but do not have the right to the source=20
> code.
>=20
>=20
>=20
> Any feedback on the above items will be most appreciated.
>=20
>=20
>=20
> C. Rose
>=20
>=20
>=20
> --
> MySQL ODBC Mailing List
> For list archives: http://lists.mysql.com/myodbc To unsubscribe:
> http://lists.mysql.com/myodbc?unsub=3Dmberman@ivesinc.com
>=20
>=20
> --
> MySQL ODBC Mailing List
> For list archives: http://lists.mysql.com/myodbc
> To unsubscribe:
http://lists.mysql.com/myodbc?unsub=3Dretheoff@gmail.com
>=20
>=20


--
Greg Fischer
1st Byte Solutions
http://www.1stbyte.com

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:
http://lists.mysql.com/myodbc?unsub=3Dmberman@ivesinc.com


--
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

Re: MyODBC

I think the question was about MyODBC licensing, was it not? Access
has nothing to do with it. But I am glad you brought that up if
someone else needed to know.

On 7/21/05, Berman, Mikhail wrote:
>=20
> Dear Greg,
>=20
> Microsoft produces "Microsoft Office Access2003 Developer Extensions" to
> create legal run-time applications, that does not require MS-Access to
> be installed on each client's PC.
>=20
> Mikhail Berman
>=20
> -----Original Message-----
> From: Greg Fischer [mailto:retheoff@gmail.com]
> Sent: Thursday, July 21, 2005 12:23 PM
> To: myodbc@lists.mysql.com; Christine Rose
> Subject: Re: MyODBC
>=20
> Not an Attorney, but I think if you have "closed source" app distributed
> with Mysql, you need a license. Maybe I am reading wrong, but here's
> some links:
>=20
> http://www.mysql.com/company/legal/licensing/index.html
> http://www.mysql.com/company/legal/licensing/opensource-lice nse.html
>=20
> About the dll's, I dont know what is entailed, I bet you could hunt down
> the dll's and script it into your app installer somehow.
>=20
> Greg
>=20
> On 7/20/05, Berman, Mikhail wrote:
> >
> > Below is explanation and a sample code to refresh linked table, taking
>=20
> > from MS-Access help on "Refresh Link" method
> >
> > ==================== ===3D=
==================== =====3D=
==================== ==
> > ==
> > ==================== ===3D=
==================== =====3D=
==================== ==
> > ==
> > RefreshLink Method
> >
> >
> > Updates the connection information for a linked table (Microsoft Jet
> > workspaces only).
> >
> > Syntax
> >
> > tabledef.RefreshLink
> >
> > The tabledef placeholder specifies the TableDef object representing
> > the linked table whose connection information you want to update.
> >
> > Remarks
> >
> > To change the connection information for a linked table, reset the
> > Connect property of the corresponding TableDef object and then use the
>=20
> > RefreshLink method to update the information. Using RefreshLink method
>=20
> > doesn't change the linked table's properties and Relation objects.
> >
> > For this connection information to exist in all collections associated
>=20
> > with the TableDef object that represents the linked table, you must
> > use the Refresh method on each collection.
> >
> > ==================== ===3D=
==================== =====3D=
==================== ==
> > ==
> > ==================== ===3D=
==================== =====3D=
==================== =3D
> >
> > RefreshLink Method Example
> >
> > This example uses the RefreshLink method to refresh the data in a
> > linked table after its connection has been changed from one data
> > source to another. The RefreshLinkOutput procedure is required for
> > this procedure to run.
> >
> > Sub RefreshLinkX()
> >
> > Dim dbsCurrent As Database
> > Dim tdfLinked As TableDef
> >
> > ' Open a database to which a linked table can be
> > ' appended.
> > Set dbsCurrent =3D OpenDatabase("DB1.mdb")
> >
> > ' Create a linked table that points to a Microsoft
> > ' SQL Server database.
> > Set tdfLinked =3D _
> > dbsCurrent.CreateTableDef("AuthorsTable")
> >
> > ' Note: The DSN referenced below must be configured to
> > ' use Microsoft Windows NT Authentication Mode to
> > ' authorize user access to the Microsoft SQL Server.
> > tdfLinked.Connect =3D _
> > "ODBC;DATABASE=3Dpubs;DSN=3DPublishers"
> > tdfLinked.SourceTableName =3D "authors"
> > dbsCurrent.TableDefs.Append tdfLinked
> >
> > ' Display contents of linked table.
> > Debug.Print _
> > "Data from linked table connected to first source:"
> > RefreshLinkOutput dbsCurrent
> >
> > ' Change connection information for linked table and
> > ' refresh the connection in order to make the new data
> > ' available.
> >
> > ' Note: The DSN referenced below must be configured to
> > ' use Microsoft Windows NT Authentication Mode to
> > ' authorize user access to the Microsoft SQL Server.
> > tdfLinked.Connect =3D _
> > "ODBC;DATABASE=3Dpubs;DSN=3DNewPublishers"
> > tdfLinked.RefreshLink
> >
> > ' Display contents of linked table.
> > Debug.Print _
> > "Data from linked table connected to second source:"
> > RefreshLinkOutput dbsCurrent
> >
> > ' Delete linked table because this is a demonstration.
> > dbsCurrent.TableDefs.Delete tdfLinked.Name
> >
> > dbsCurrent.Close
> >
> > End Sub
> >
> > Sub RefreshLinkOutput(dbsTemp As Database)
> >
> > Dim rstRemote As Recordset
> > Dim intCount As Integer
> >
> > ' Open linked table.
> > Set rstRemote =3D _
> > dbsTemp.OpenRecordset("AuthorsTable")
> >
> > intCount =3D 0
> >
> > ' Enumerate Recordset object, but stop at 50 records.
> > With rstRemote
> > Do While Not .EOF And intCount < 50
> > Debug.Print , .Fields(0), .Fields(1)
> > intCount =3D intCount + 1
> > .MoveNext
> > Loop
> > If Not .EOF Then Debug.Print , "[more records]"
> > .Close
> > End With
> >
> > End Sub
> >
> >
> > Mikhail Berman
> >
> > -----Original Message-----
> > From: Martin King-Turner [mailto:martin.kt@nb2bc.co.uk]
> > Sent: Wednesday, July 20, 2005 10:27 AM
> > To: 'Christine Rose'; myodbc@lists.mysql.com
> > Subject: 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
>=20
> > to require the linked tables to be refreshed using the linked table
> > manager. In your scenario, this will require the linked table manager
>=20
> > 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]
> > 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.
> >
> >
> >
> > My desktop application is deployed as a complete package including
> > Access Runtime files.
> >
> >
> >
> > 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.
> >
> >
> >
> > 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=3Dmberman@ivesinc.com
> >
> >
> > --
> > MySQL ODBC Mailing List
> > For list archives: http://lists.mysql.com/myodbc
> > To unsubscribe:
> http://lists.mysql.com/myodbc?unsub=3Dretheoff@gmail.com
> >
> >
>=20
>=20
> --
> Greg Fischer
> 1st Byte Solutions
> http://www.1stbyte.com
>=20
> --
> MySQL ODBC Mailing List
> For list archives: http://lists.mysql.com/myodbc
> To unsubscribe:
> http://lists.mysql.com/myodbc?unsub=3Dmberman@ivesinc.com
>=20
>=20


--=20
Greg Fischer
1st Byte Solutions
http://www.1stbyte.com

--
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