At 03:17 PM 11/17/2008, Emmitt Dove wrote:
Bob,
Here's what we do:
1) With STATICDB OFF, SCONNECT / SATTACH; now the SATTACHed
table is defined in the main database and available to all
2) All users run with STATICDB ON, so 1) must be performed by a
single user when no one else is connected
3) Normal users do:
a. SCONNECT
b. Whatever operations are to be performed using the SATTACHed table
c. SDISCONNECT
The reason for the SDISCONNECT is to release the operating
system-level database open on the remote database. As long as a
user has an SCONNECT in effect, R:BASE holds the database files open.
Even if you don't run with STATICDB ON, the above can/should
apply. You only need to SATTACH a table once. There is no harm in
leaving it that way. You do not have to SDETACH the table in order
to SDISCONNECT. Any SATTACHed tables are visible to all users,
UNLESS the SATTACH is performed while STATICDB is ON. In this case,
the SATTACH only applies to the user who issued the SATTACH and will
go away when the user DISConnects.
In addition ...
Using the latest and greatest version/updates of R:BASE 7.6, C/S:I 7.6,
Turbo V-8, and R:BASE eXtreme 9.0 for Windows, you may take advantage
of "User Specific" SATTACHed tables.
Syntax:
SATTACH TEMPORARY tablename AS tablealias USING ...
The optional TEMPORARY parameter allows you to create a Temporary Table
with the SATTACH command and all supported parameters. The temporary
tables will disappear when the database is DISConnected.
Use this option to take the exact snapshot of the sever table to manage
and analyze the data as you wish.
Note:
Any changes made to the temporary table will not be reflected upon the
original SQL data source.
The sole purpose of this new feature is to let R:BASE attach server
tables as TEMPORARY tables specific to that User/R:BASE session even
when the database is connected with STATICDB ON.
Imagine the possibilities!
Very Best R:egards,
Razzak.
