Hi Grigore

Thanks for dropping in

>I'm not sure there is need to check for idleness. Actually ... it's safe to execute SQLIdleDisconnect() immediately after the downloading data for report.

I need to drop some information here.

Our app is fully c/s. We just cannot stop the connection after every process as most of them are so limited in scope (everytime the user moves one records down a listbox, the c/s connection handle is active).

We definitely want to SQLIDLEDISCONNECT() after a period of idle time (coffee or tea time). But that's difficult to catch. We may resort to activating some kind of timer every time the application is back to "read event" state.

you mentioned SQLSetProp(0,"IdleTimeout",1). This is what we use up to now.
It is supposed to fit the bill but...

this function is buggy. It will work or not depending on odbc (it looks like it is implemented at the driver level) and won't restart automatically as nicely as SQLIDLEDISCONNECT().

Hence the idea of using the new fresh SQLIDLEDISCONNECT() function. Which is a nice thing but requires explicit calling.

Francis

>>VFP9 offers a new SQLIDLEDISCONNECT( ) Function. According to on-line documentation it "allows a SQL pass-through connection or connections to be temporarily disconnected".