More doubts on: non reentrancy for TCP/IP VIs

[rolfk]

sumitrishi wrote:

> Thanks Rolf that was pretty informative.Furthering my efforts I was
> looking at the property node for connection interface I have a feeling
> that if anything has to be done it should be done at the point when
> the connection is made . There is this particular property called
> 'mode' and one of the constant settings for it is 'adModeRecursive'.

I couldn't really say for sure. I never really used the ADO based SQL
Toolkit at all. Mostly I use my own ODBC based library.

> Could that be the place for me to look at ? Somehow for me setting it
> has been generating error .Can you please tell me what actually is
> 'mode'. I am appreciative of all your help. -Fellow ex NI (
I was
> with India Branch, although I spent most of my time working with CW++)

I think there are other things to look at. One thing could be that the
Transaction does work as some lock. Definitely for a recordset modified
in there but possibly for the table.

Look also at DOS_AppSrvr_ExecuteSQL.vi. In there you have a LockType to
the Recordset.Open method. This could block any other access to the same
table until the recordset is closed with End SQL. But a less restrictive
lock could give problems when the same records are modified at that
moment by someone else.

Also I have seen that the DOGS_AppSrvr_ExecutePreparedSQL returns for
instance the command refnum which should be closed at some point by SQL
End. Otherwise they will accumulate and need to be closed when the
connection is closed in some sort of garpage collection which can be
time consuming.

Rolf Kalbermatter

[Feroz]

Hi Sumitrishi,
I found a document on MSDN that gives you a description about the differents modes you are refering to

ConnectModeEnum

I hope this helps

Sincerely,
Feroz