Bob Razzak has writen to nice programs to check whwter a database is sconnected or not, after that even some nice program to where a table is sattached or not.
I can post you razzak program tomorrow if you want. As far as I understand an sconnected database stays connect for all users until someone disconnect it. Gunnar Ekblad Kontema IT AB Hästholmsvägen 32 131 30 Nacka Sweden -----Ursprungligt meddelande----- Från: [email protected] [mailto:[EMAIL PROTECTED] För [EMAIL PROTECTED] Skickat: den 17 november 2008 18:29 Till: RBASE-L Mailing List Ämne: [RBASE-L] - SCONNECT / SDISCONNECT This is something I should already know, but did not find a distinct answer in my first help search. Is Sconnect / SDisconnect session unique or database unique? I.E. 5 users connected to the same database, all five accessing an ODBC table, if one session issues a SDisconnect will this effect the other users? During brief testing, it appears that SCONNECT / SDISCONNECT does not effect other users, however SATTACH or SDETACH does effect other users. If I have a table SATTACHED and issue a SDISCONNECT, the table still functions, it appears the SDISCONNECT has no impact. If I SCONNECT and SATTACH an ODBC table in session one, session two can access this table and never have to SCONNECT. So this seems to indicate that SCONNECT is database specific and not session specific. However, if I issue a DISCONNECT, it does not effect other users at all. I can Disconnect in session one and session two can still access the table fine. So my question is, do I need to worry about SCONNECT or SDISCONNECT in a multi user environment? My initial tests seem to say no.? Certainly SATTACH and SDETACH makes a big difference. Thanks, -Bob -- Thompson Technology Consultants LaPorte, IN 46350 219-363-7441
