I encountered an issue with ODBC connectivity, very similar to what you are reporting. The solution (as incomprehensible as it sounds) was the length of the user name and password. Once I used a user ID that was 8 characters (or less) and a password that was 9 characters (or less), my connectivity issues were resolved.
Just my $.02. Regards, Robert Original Message: ----------------- From: Kevin King [EMAIL PROTECTED] Date: Wed, 11 Jan 2006 06:25:17 -0700 To: u2-users@listserver.u2ug.org Subject: RE: [U2] ODBC Difficulties I forgot to mention that I'm using the same user ID on both systems, so it would seem that it's not the privilege file. Also, the fact that the errors get returned immediately - as if it doesn't even make an effort to connect - makes me think something is amiss with the driver. There should be no difference installing as a User DSN vs. System DSN, right? -Kevin [EMAIL PROTECTED] http://www.PrecisOnline.com ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ . ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
