Albert:
Can you elaborate on the ON FIRST CONNECT?
What I have done so far is to change the exit code as follows:
-- Other code here
SET VAR vconnections =(CVAL('CONNECTIONS'))
DISC
IF vconnections = 1 THEN
DEL *.$$$
DEL 0*.rmd
DEL 1*.rmd
DEL 2*.rmd
DEL 3*.rmd
DEL 4*.rmd
DEL 5*.rmd
DEL 6*.rmd
DEL 7*.rmd
DEL 8*.rmd
DEL 9*.rmd
ENDIF
EXIT
Note that you have to use the (CVAL('CONNECTIONS')) before you disconnect
otherwise it will show 0 (zero); also, if a session was terminated
abnormally, the session will show in the number of connections.
Javier,
Javier Valencia, PE
President
Valencia Technology Group, L.L.C.
14315 S. Twilight Ln, Suite #14
Olathe, Kansas 66062-4578
Office (913)829-0888
Fax (913)649-2904
Cell (913)915-3137
================================================
Attention:
The information contained in this message and or attachments is intended
only for the person or entity to which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this information by persons or entities other than the intended recipient
is prohibited. If you received this in error, please contact the sender and
delete the material from all system and destroy all copies.
======================================================
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] Behalf Of Albert Berry
Sent: Monday, August 15, 2005 8:54 PM
To: RBG7-L Mailing List
Subject: [RBG7-L] - RE: Cloberring other people's $$$ files.
Larry, Javier et al.
Perhaps this is a good use for an ON FIRST CONNECT applied to the database.
--- Javier Valencia <[EMAIL PROTECTED]> wrote:
> Larry:
> This would explain some problem my users have been having when someone
else
> logged out early. Normally they all log in and log out at roughly the same
> time so it has not been a huge issue yet. I could put code on the logout
> routine to check whether there are other user logged in and if yes it
would
> not delete the *$$$ files, in other words the last user to log out would
> delete all the temporary files...
> Javier,
>
> Javier Valencia, PE
> President
> Valencia Technology Group, L.L.C.
> 14315 S. Twilight Ln, Suite #14
> Olathe, Kansas 66062-4578
> Office (913)829-0888
> Fax (913)649-2904
> Cell (913)915-3137
> ================================================
> Attention:
> The information contained in this message and or attachments is intended
> only for the person or entity to which it is addressed and may contain
> confidential and/or privileged material. Any review, retransmission,
> dissemination or other use of, or taking of any action in reliance upon,
> this information by persons or entities other than the intended recipient
> is prohibited. If you received this in error, please contact the sender
and
> delete the material from all system and destroy all copies.
> ======================================================
>
> -----Original Message-----
> From: [email protected] [mailto:[EMAIL PROTECTED] Behalf Of Lawrence
Lustig
> Sent: Monday, August 15, 2005 9:16 AM
> To: RBG7-L Mailing List
> Subject: [RBG7-L] - Cloberring other people's $$$ files.
>
> Although I set the scratch directory to the user's temp directory, I still
> accumulate a lot of $$$ files in the startup directory in multi-user
> situations. To protect against this, I have always included an ERASE
*.$$$
> in
> command files (since R:Base never erases the open files from the current
> session).
>
> Recently (with 7.1), I've noticed a couple of occurences in which I've
been
> able to clobber _another user's_ R:Base session by erasing all the $$$
files
> in
> the startup directory. In other words, files which R:Base used to not
erase
> are now eraseable from a different R:Base session.
>
> Has anyone else noticed a similar change? How do people deal with the
> danger
> of clobbering another session by erasing a temp file?
> --
> Larry
>
>
Albert Berry
Management Consultant
RR2 - 1252 Ponderosa Drive
Sparwood BC, V0B 2G2
Canada
(250) 425-5806
(250) 425-7259
(708) 575-3952 (fax)
[EMAIL PROTECTED]
