Bob Once you SCONNECT and then SATTACH a table anyone using that table must use the same type of SCONNECT. For example if you SCONNECT using a DSN and then SATTACH sometable. If I want to use sometable then I must have the same DSN on my workstation. When I try to use the sometable the SCONNECT is transparent as long as I have the same DSN.
If a number of users will be using the same SATTACH table then I don't SDETACH it. Buddy From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, November 17, 2008 12:29 PM To: RBASE-L Mailing List Subject: [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
