Recent content by woyakj

It has actually been several months now since I implemented this, so I may be forgetting something, but I think that as long as the ODBC connection tests fine on the box you want to use it on, and you have your provider string and the other settings right under your linked server ODBC settings...

Klar I got this to work in a different fashion than you seem to be trying. What I did was setup (using the Progress SQL92 ODBC driver) an ODBC connection (system DSN) on the server I wanted to set it up as a linked server on, and then added the linked server in Enterprise Manager as an MS OLE...

You are THE MAN :-) That was it.. I never even thought about that, but it was set to "Be made without using a security context". I switched it to "Be made using the login's current security context" and it worked! Thanks so much. You have rescued my day :-) --jason

Thanks for the response! I tried this, but got the exact same error message. Here is the modified Provider string I used: DSN=skyward;DB=skyward;UID=sysprogress;PWD=<BLANKED>;HOST=67.53.75.200;PORT=23473 and once again I get the same error. I notice that you are connecting by name and I am...

the whole thing.. ;-) Here is my ODBC setup: Product Name: MERANT 3.60 32-BIT PROGRESS Data Source: SKYWARD Provider String: DRIVER={DataDirect 5.0 Progress SQL92};UID=sysprogress;PWD=<BLANKED>;DatabaseName=skyward;PORTNUMBER=23473;HOSTNAME=67.53.75.200 catalog...

Did you ever get this working? I am running into the same issue and would love to solve this! Thanks!