>About permanent connections, I've checked and I've found that, if IdleTimeout is set , foxpro will auto disconnect from server when time specified is elapsed. When TABLEUPDATE() is executed, it will try to connect again to the server. If fail, with AERROR() function we can see the ODBC driver message that server is unavailable. The funiest part is that if you wait the time specified in IdleTimeout and in the mean time you restore the connection, Foxpro will reconnect again and will execute the update. I would like a function like SqlReConnect() that can do the same thing.
>

If you lose your connection (for whatever reason) TableUpdate will not work even if you reconnect. Not even if the connection handle that you get when you reconnect is the same as the one before the connection was lost. My advise would be that you do some testing on this to see what can go wrong if you lose the connection.



>About SPT, it is not like with remote views? It is not the same connection handle needed to SQLCOMMIT() ?
>I mean, I connect and I have a connection handle, work on cursor and want to commit changes but the connection is lost. What next? I can save changes and commit through another connection handle?
>

With SPT you don't need a permanent connection. You can connect, get data, disconnect, play with data, connect again, and submit changes. Yet, SPT does not work with TableUpdate out of the box. You will need to change a few properties (which I don't remember right now) in your SPT cursor before you can use a tableupdate on it.

Post a second question asking how to make an SPT cursor updateable via TableUpdate. I am sure somebody will remember what properties need to be set.