![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
Last Dec I posted a message asking for help in determining why Central was working ok with jConnect but terribly via iAnywhere JDBC driver. In the course of the investigation, I put TCPIP in as a connection parameter during the login process and the problem suddenly disappeared. I'm now using a new PC (windows 2K3) and am running into the problem again. This time I created the database using the migration wizard to migrate it from ASE (supplemented by extra SQL to define default values and primary keys which didn't migrate).. I just now unloaded and reloaded to see if that would help, but it had no effect (other than to create a MUCH large database). I've attached the log created by Central (as advised last time). Any suggestions would be welcome (I posted this 2 times in last few days and it ended up on the old topic so I'm doing it again with a new topic in the hopes that it will be seen..sorry if that was inappropriate..) |
#2
| |||
| |||
|
|
ODBC tracing running |

![]() |
| Thread Tools | |
| Display Modes | |
| |