- Create an ODBC Data Source to your MySQL Server (requires MyODBC connector).
- Add the following to your SQL.INI:
sqlodb32 must be listed *before* sqlws32
- Set SqlDatabase, SqlUsername und SqlPassword according to your situation and call SqlConnect.
- You should be done.
You'll probably find more postings about MyQL in this bb. Experiment and have a look at the other settings for SQL.INI. Pay attention to various datatypes, I remember finding it convenient to convert integers to strings as part of the sql statement (I think some truncation was going on).
by the time im using TD6.2 but i guess this has nothing to say... at least in this case it doesn't.
OS: windows 7
Apache: xampp 1.8
Permissions: ALL PRIVILEGS
Adds to sql.ini:
Added MySQL-ODBC Driver to MyODBCConnector
Code: Select all
On SAM_CreateComplete ! ODBC-Data Set SqlDatabase = "centrua" Set SqlUser = "gupta" Set SqlPassword = "123456"
Code: Select all
On SAM_Click If SqlConnect( MySQL_handle ) ! (connection established) Call DebugMessage( "Verbindung wurde hergestellt" ) Else ! (connection failed) Call DebugMessage( "Verbindung leider fehlgeschlagen"
cannot open database
Option to Continue or Stop DBFOR SQLBASE: The specified database cannot be found. SQLBase cannot find the file named "x:\dbdir\dbname\dbname.DBS" where
x:\dbdir is either the default, c:\SQLBASE, or modified with the DBDIR SQL.INI configuration keyword.
In a multiuser network configuration, this error indicates that your network is working correctly, but the database system was unable to
locate the specified database filename.
FOR NON-SQLBASE DATABASES: This problem can also occur with a SQLGateway when leaving out the protocol type in the SERVERNAME
parameter that the client uses to communicate with the gateway (like SQLNBIOS). For example,
DBNAME=DB2DBMS, SQLQUEUE, SQLNBIOS
will nott allow a remote client process (using SQLNBIOS on the LAN to communicate with the SQLGateway machine) to connect to the SQLGateway machine.
For SPX connectivity from DOS or MS Windows to a Unixware SQLBase Server check for the omission of the "serverpath=..." parameter in the SQL.INI file under the client section.
Remedy: Verify the database file exists. The default drive letter and dbdirname is c:\SQLBASE unless overridden with a DBDIR SQL.INI
configuration keyword parameter. Verify the DBDIR keyword is not missing or pointing to a wrong database directory. Verify
the DBNAME keyword is specified for the named database. Verify the SERVER keyword is not missing or conflicting with other
network server names. In your CONFIG.SYS file, verify at least 40 files set with the FILES=40 parameter. If the server was
being initialized while the connection was tried, retry the connection after the server has initialized. If all of the
above fails, try using a different database name or try connecting to the database in single user mode at the same
machine. If you can connect with a local engine it probably indicates a network configuration error exists. If you can
connect with a new database name it probably indicates a previously named database was never properly initialized.
On Continue i get Connection failed
Can someone help me there ?
Who is online
Users browsing this forum: [Ccbot] and 0 guests