KMcElhiney
asked on
Error linking tables from MS Access 2003 to Sybase ASE
This is a weird one. After installing the Sybase ASE 15.03 drivers on an XP computer, I created a DSN for a Sybase database running on a network server and tested the connection. It worked fine. Then, I went into MS Access 2003 and attempted to link to one of the Sybase tables using the ODBC driver I just created. It allowed me to create the link, but when I tried to open the table, it displayed the first couple of rows and then prompted me for the password again. It then kept bringing up this error message over and over again and finally failed with an ODBC error that caused MS Access to close down.
I have no idea what is causing this problem. Has anyone seen this problem before?
Thanks in advance,
Kevin McElhiney
I have no idea what is causing this problem. Has anyone seen this problem before?
Thanks in advance,
Kevin McElhiney
ASKER
I tried User, System, and File DSN's. Same problem each time...
Yes, it is ASE 15.0.3 on a big Unix box.
I am running XP SP3 so I have the latest MDAC, I couldn't find any applicable patches.
I haven't tried opening a table from Excel, but it seems likely that I would get the same result.
Yes, it is ASE 15.0.3 on a big Unix box.
I am running XP SP3 so I have the latest MDAC, I couldn't find any applicable patches.
I haven't tried opening a table from Excel, but it seems likely that I would get the same result.
Try it anyway... If it works we know it's an issue dith Access; if it doesn't then we suspect ODBC or ASE.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Was this a User or System DSN?
Forgive the impertinent question, but are you in fact connecting to a Sybase ASE 15.0.3 system? :)
You say this is on XP... possibly an issue with the MDAC version? Have you applied all patches MS recommends for your system, and then specifically sought and applied the latest MDAC patch? (I find it isn't included in Windows/Microsoft Update lists.)
To try to narrow down where the problem is - can you use this ODBC DSN OK in other apps? ie. try it in Excel, try it in a previous version of Access if you have one handy, etc.