Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Ben Draper — — source: Informix-list mailing list archive (1991-1998)
Thanks in advance to anyone who might shed some light on the problem
below...
We have a stored procedure which we want to call from within VB.
The procedure begins a transaction, locks some tables, inserts some rows,
and commits the transaction. It works as expected when called from dbaccess
on the server.
When the stored procedure is called from the vb app, the stored procedure
fails with an exception -535 'already in transaction' however no
transaction was ever started in VB. (we are assuming that sequelink
implicitly starts a transaction)
This error can be bypassed by explicitly starting a transaction within VB
before calling the SP and placing a rollback work statement in the beginning
of the SP. (Without the rollback an ODBC error is returned
[INTERSOLV][ODBC SequeLink driver][Informix][S1000]Not in transaction)
Has anyone encountered this particular error and know a better way around it
than we found.
DETAILS
---------------
Informix 7.30 UC7
ODBC: Merant sequelink
visual basic 6 connecting with active data objects
==========================================
Ben Draper
DBA / Developer
The MathWorks, Inc.
bdraper@mathworks.com
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.