Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SQL-92 Connection to Multiple databases

Status
Not open for further replies.

zolofto70

Programmer
Jul 10, 2002
1
US
Just curious. Are there any ODBC drivers that allow a connection to multiple V9.x databases?
In version 8 this could be accomplished with the Merant driver. But we have lost this option in the move to 9 and SQL-92.
 
I'm trying to do the same thing. I've been looking at the OpenLink ( ODBC drivers. They have a Progess script that creates a TABLEVIEW .pf and .dat file that allows one to connect to multiple db (so they say). The reason I'm on this forum is I'm having trouble getting it to work. I'm getting an error message that my db name is greater than 11 characters, which it is not by the way.

If you try these and get it to work please let me know.
Thanks
Bernie
 
Hi guys,
I use openlink ODBC and successfully connect to any progress databases. I haven't tried using it to connect to multiple databases though, cause I never had the need to do it. I can see though how you could specify multiple database connections in the pf file, but I don't know how the dat file would distinguish the tables and fields for multiple databases. Bernie are you tryinig to connect as a single user, therefore typing in the full path of your database? Just trying to figure out your error.

Regards, Carmelo Brual (IT Specialist)
Progress DBA
Cognos Impromptu Administrator
Cognos Impromptu Reporting
 
Carmelo,
Both the Tableview.pf and tableview.dat files are generated by a openlink supplied script (see: ...\openlink\lite32\setup.p).

The tableview.pf file contains one connection string for each db (as you said) and the tableview.dat contains a list of dbs, tables in the db and column in each table. My db names in both of these files do not include the path.

Once you generate these two files using the setup.p script you enter their names in the ODBC setup screen on the Progress Tab. Under Database Options you put the full path and file name of the tableview.pf file. Under Table View you put the full path and file name of the tableview.dat file.

When I do this and press Test Connect I get an error:
"CONNECTION ERROR:[OpenLink][ODBC][Progress Server] 'Your database name is longer than 11 characters (448), SQLSTATE=s1000.

I get the same error if I try to use the ODBC DSN in an application.

These databases are in use by applications for many years (that is they are not new).

Any help would be appreciated.
Thanks
Bernie
 
Hi Bernie,
Can you give me the following nformation.
-The 3 lines that are in the ODBC progress parameters.
-The info in your pf file
-The version of progress your database is on.
-The version of openlink you are using.
-The actual name of the database.
What I will do (if I have the same version of progress you use) is create a database with the same info that you provided so I can troubleshoot it. If you want you can email it to me direct (Carmelo.Brual@apak.com)

Regards, Carmelo Brual (IT Specialist)
Progress DBA
Cognos Impromptu Administrator
Cognos Impromptu Reporting
 
Carmelo,
Thank you very much for your offer. While I was getting this info together for you I found out that I needed -pf preceeding the tableview.pf file name I supplied to OpenLink.

To refresh, one has to specify the tableview.pf file name and path in the 'database options' in the Progress Tab of the ODBC DSN manager. I guess by leaving off the -pf, Progress thought I was giving it a DB name and said the DB name was too long.

It's working now. So OpenLink supports connection to multiple Progress data bases using one ODBC DSN! This is really smooth.

Thanks again for your help.
Bernie McGuire
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top