Post
by Jeff Luther » 03 Jul 2008, 17:03
Posted by: Jeff Luther
Well, I don't know the internals of how SQLTalk gets itself set up, Jostein,
but I see from #135 that:
00135 SQL ICN Invalid cursor number
Reason: The application program is attempting to perform a function call and
is using an invalid cursor number. Or, the application program may be using
an old or mismatching version of a .DLL file. Also, if this is a shared
cursor, it may be that the shared cursor is no longer valid because the
owner application has been terminated.
The "old or mismatching version of a .DLL file" might be a clue. Where are
you running SQLTalk? It's a little confusing because I see on my std. setup
that there's a SQLTalk in my TD install directory. There's also a SQLTalk in
the SQLBase directory, which is under the TD install dir.
I have a shortcut in a desktop folder that points to the SQLBase version,
though I just d-clicked on the one in the TD dir. and it loaded ok as well.
Check to be sure all the DLLs have the same date. for my SP2 I have them
dated 4/4/2008.
"let me know how to fix this" - Maybe Mike V. will visit here and expand on
my reply, but at be sure of the dates of the DLLs and that your sql.ini is
still correct.
Best regards,
Jeff Luther
Unify Corporation