ODBC connection for Raiser's Edge 6 --SqlAnywher 5.0

Yes I know this product is ancient and should be somewhere however...... money......

What I would like to be able to do is create an ODBC connection so I can run a query tool to look at the DB structure.  I have the driver already and a registry entry for Sybase SQL Anywhere with driver info.  I have the EngineName, DatabaseName, DatabaseFile and all the possible ini files from the actual application for info.

When I try to connect while creating a DSN file in ODBC (Data Sources) urilitiy, it fails.

Questions:  What are the essential pieces needed to connect to this DB?

What is the best way to establish a connection?

Does anyone have the syntax for a working connection?

Basically.... Help!!!!

Thanks in advance,

smantzDirector of TechnologyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Joe WoodhousePrincipal ConsultantCommented:
You'll need the SQL Anywhere 5.x ODBC driver. More recent ones may still work with it, because I don't like your chances of finding that driver anywhere if you don't already have it.

You'll need to know a login/username and password, and you may need to embed those in the connection string or through the ODBC properties.

You may need to create a "System" ODBC data source rather than a "User" one... I recall the old drivers were fussy about that. Probably best to make sure there aren't any spaces in the directory path where the ODBC driver and database files are, early versions didn't like those either.

Are you getting any error message?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
smantzDirector of TechnologyAuthor Commented:
Well, I believe one of the errors was error 193.  I'm going to rerun it this morning.  One of the items I keep finding in my readings is the need for "dbclient.exe", which does show up in the actual application files and scripting.  I'm not sure what this does but seems unique to SQL Anywhere Version 5.x.x.  I will post any errors as I work this morning.
Thanks for the response!!! -SM
smantzDirector of TechnologyAuthor Commented:
Looking closer the actual file that is called by the OBDC.ini file in C:\System is DBCLIENW.exe.  There are 2 ini files created by application that are found in C:\SYSTEM, they are: ODBC.ini and ODBCINST.ini.  The first is rather long the, the second is shorter.  Would it help to send these along?  I'm wondering if and how I can fit these into a registry entry so the information is available to other programs like a Query Analyzer.  Does this make sense?
Powerful Yet Easy-to-Use Network Monitoring

Identify excessive bandwidth utilization or unexpected application traffic with SolarWinds Bandwidth Analyzer Pack.

Joe WoodhousePrincipal ConsultantCommented:
That's the built-in SQL Anywhere client tool. I'm surprised the ODBC data source is looking for it... Do you still have the source install for the SQL Anywhere database? If not you might be able to use a more modern version and install the client from there.

I'm not sure I understand why the ODBC data source (in principle usable by any client) has a hard-coded reference to a particular client tool, though...
smantzDirector of TechnologyAuthor Commented:
Sorry it has taken a while to get back.  As far as I found thus far, it seems version 5.x was the only version to use the DBclient.exe

I do have the 32 drivers as well ( they were on the app install disk) so I installed them along with the DBClient (32 bit).

I still having an issue getting the ODBC administrator in Windows to connect. I'm using win7 pro 32 bit on both the test server and the client.  The app actually has three ini files.  I'm guessing I need to take the right combination of items and maybe put the in the registry as, that is what happens these days.  

Would it help to give the information from the ini files?

Joe WoodhousePrincipal ConsultantCommented:
The INI files are written to by the ODBC Administrator tool when you set up a data source. Better to go through that control panel I think.
smantzDirector of TechnologyAuthor Commented:
Well, it looks like the driver disk modified the HKey_CurrentUser and created a user profile which can be seen in the ODBC administrator.  I crreated a system file to match.  Since I'm not receiving any errors there and I can enter the configuration screen, I guess they are talking to one another.  This may be a bad assumption, as I don't know if they really are connected.  When I try and create a file profile in the ODBC, itappears I get a configuration screen.  The problem is, it always asks for a user ID and password and I'm not sure if I'm getting it right.
I have a little more time tomorrow so I can try to see if I can get connected with a string.
THe ultimate goal, once again, is to be able to have a profile or string that will connect so I can use a query analyzer tool to look at DB tables.
If you have any ideas please fell free to post them.
Any errors or messages I get, I'll post.
smantzDirector of TechnologyAuthor Commented:
I have not totally gotten things to work.  I am doing a new post.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Sybase Database

From novice to tech pro — start learning today.