how have you guys dealt with client stations disconnecting due to odbc
is there anything on the server side that can help the problem?? or is it
just the vb coder's responsibility?
This is a newbie question but, what do you mean by a ODBC timeout? I have
an application that uses ODBC to update an oracle database on a RS/6000 and
I have problems with inconsistant updates to the database.
Quote:> If it is an ODBC timeout, then you fix it on the client.
> how have you guys dealt with client stations disconnecting due to odbc
> is there anything on the server side that can help the problem?? or is it
> just the vb coder's responsibility?
Default is 10 secs maybe you need longer? Setting to 0 means it never
Phil Britton (Senior Consultant)
"The opinions here are mine, I thought of them, they are my opinions"
http://www.prismtechnologies.com 5th Avenue Business Park
Tel. +44 (0)191 4979900 Gateshead NE11 0NB
FAX. +44 (0)191 4979901 United Kingdom
I have 2 Recordsets on 2 different applications communicating with the same
-=The first Recordset is opened with=-
m_pGlobal_RS->Open(adCmd, m_pConnection.GetInterfacePtr(), adOpenKeyset,
-=The second Recordset is opened with=-
local_RS->Open(adCmd, m_pConnection.GetInterfacePtr(), adOpenKeyset,
* adCmd is a simple SELECT statement that is the SAME for both recordsets.
The code order is roughly this
Change fields on m_pGlobal_RS
MoveNext on all rows of m_pGlobal_RS until EOF then MoveFirst // since
pessimistic every row op sends update
I then fire an event to another application which opens local_RS.
It is random whether the data opened by the second RS is the pre-update data
or the post-update data. How can this be? I opened the connection
with the default synchronous option, isn't this asynchronous behavior?
Thanks for the help,