Buddy, Does it affect the sconnected database if you do a reload on the sconnected database (while it is sdisconnected) with the table still sattach'd. (in my app both databases are rbase).
Bernie Lis ----- Original Message ----- From: "Walker, Buddy" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> Sent: Sunday, January 12, 2003 5:50 PM Subject: [RBASE-L] - RE: SCONNECT & SATTACH > Bernie > I do this all the time. I SCONNECT right after I CONNECT to the > database therefor I don't have to do sattach. I don't sdetach a table > unless it is rarely used. Data is always up to date.. > > Buddy > > -----Original Message----- > From: Bernard Lis [mailto:[EMAIL PROTECTED]] > Sent: Sun 1/12/2003 4:27 PM > To: [EMAIL PROTECTED] > Cc: > Subject: [RBASE-L] - RE: SCONNECT & SATTACH > > > > Razzak, > Please clarify -- > If you sdisconnect, the attached file appears to be still in the > current > database but not available for use? > if you later sconnect without sattaching, do you have the up-to-date > table > or just as of originally attaching? > > I choose to sdisconnect and disattach when exiting the current database. > Is > this necessary? > > Bernie Lis > > ----- Original Message ----- > From: "tellef" <[EMAIL PROTECTED]> > To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> > Sent: Sunday, January 12, 2003 12:40 PM > Subject: [RBASE-L] - RE: SCONNECT & SATTACH > > > > >In order to avoid that dialog box, you'll need to ONLY use > >SCONNect DSNName IDENTIFIED BY UserID Password > >command right after you connect the database, every time.< > > Razzak, you're right! How about that! I just tried it, > and if you ONLY do the SCONNECT without the SATTACH, then > those attached tables stay there and when you need to use > them it doesn't ask for connection data. I was under the > impression that you always had to attach them. To me it > didn't seem to make sense that disconnecting the database > also disconnects the SCONNECT'd database bit still keeps > the attached tables around. > > > Karen >
