ODBC Translator Error

[Elysynn]

Hello,

I am trying to set up an ODBC link in the ODBC Administrator and when I try to load the translator I get the following Error Message:

"The setup routines for the Sybase SQL Anywhere 5.0 Translator could not be loaded. You may be low on memory and need to quit a few applications."

I am running an XP system with a gig of memory so I hardly think that is the problem. I am learning all of this on the fly, so I am uncertain what I should do next. Is this a registry issue, and if so could someone explain to me how to fix it? Or is it possibly a restriction on my permissions by the Admins?

A little bit more background... The ODBC link already exists as a System DSN on my computer. However it is configured for our local server. I am trying to connect to the same database on a different server (hence it has the same Database Name). If I try and modify the server name on the existing connection it resets back to our local server. (This leads me to believe it is a permissions issue...) If I try and make a new one with the other server information, I get the error listed above.

Any insight that you provide will be greatly appreciated. If I missed something that has already been posted, please point me to it and I will gladly read up.

Thanks Again,
Elysynn

 

[ArtieChoke]

Still to this day they use that $#@ error message - argh! I believe it means you are missing the dll file (or it is the wrong version) that ODBC uses to connect. Or it could be set up wrong in the registry. Or it could be a permission issue. I will list some trouble shooting steps below. One other thing to try is to create a user DSN with the same name. You should have privs for this and it will override the system DSN (it will get picked first). Of course, this will only worked when you are logged on.

Trouble-shooting tips:
Check the drivers tab and look for the driver in the list. If it's there, check that it exists in the location specified. If that's okay, you'll need to check the registry entries for the driver to verify everything is set up properly.

To check the registry:
Navigate to this key:
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\

Then find the Sybase entry. Verify both the driver and setup entries are the same and use the correct location. If that's okay, check the entry for the DSN in at
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\

If everything checks out, it's probably a permission issue, either in the registry or with the driver files.

"I think we're all Bozos on this bus!" - Firesign Theatre

 

[Elysynn]

Thank you, ArtieChoke for your response.

After a short chat with the IT folks, it has been determined that this is indeed a permissions issue. So, given the scope of my project I am redirecting my efforts to learning how to create DSN less connections. (Which is proving to be an interesting endeavor)

Thanks again!
Elysynn

 

[ArtieChoke]

Assuming you are using VB w/ ADO, check out this site for connection strings:

http://www.connectionstrings.com/

"I think we're all Bozos on this bus!" - Firesign Theatre