Hi,
First you are setting twice timeout (60 and 135)
Second
I think you have to add some code which calls a routine that closes the
database and the program correctly.
It looks like this:
SET TIMEOUT 60
SET VARIABLE RBTI_TIMEOUT TEXT = 'Program_close.rmd'
As soon as the timeout is reached the called program will be executed
The routine 'program_close.rmd' contains statements like this:
DISCONNECT
EXIT
RETURN
Make sure you end up with the return
Also take care you refer to the correct directory in which
'Program_close.rmd' is situated
A good way to refer to the correct directory is to store the directoryname
in a variable, when you start your application, like this:
SET VAR G_QUOTE = (CHAR(39))
SET VAR G_DIR_DB = (CVAL('CURRDIR'))
SET VAR G_CLOSE = (.G_QUOTE + .G_DIR_DB + '\Program_close.rmd' + . G_QUOTE)
SET VARIABLE RBTI_TIMEOUT TEXT = &G_CLOSE
N.B. I surround the directory name + program name with quotes (stored in
the variable G_QUOTE).
Then I am sure the command is also executed in case of spaces in the
directory name
Hope this helps
Tony
From: [email protected] [mailto:[email protected]] On Behalf Of Paul Buckley
Sent: woensdag 9 november 2011 20:18
To: RBASE-L Mailing List
Subject: [RBASE-L] - Problem with Application Exiting to R:BASE and not to
Windows
I'm running the latest version of eXtreme 9.1 (64) and have Windows 7
workstations connecting to a Windows Server 2008R2 server using Remote
Desktop & Terminal Services. The startup file is shown below. After
running for 2-4 hours if a user exits the main menu they end up in R:BASE
and not back in Windows.
I can run it & exit 20-30 times without this happening, it seems to happen
"over time". Can anyone give me some "blue's clues" of what to look for?
I'm tapped out.
Thanks,
Paul
"Startup File"
*( start.mac )
SET MULTI ON
CONNECT xyz
SET MESSAGES OFF
SET ERROR MESSAGES OFF
SET TIMEOUT 60
SET QUOTES='
SET MANY=%
SET SINGLE=_
SET NULL ' '
SET DATE SEQ mmddyy
SET TIMEOUT 135
EDIT USING mainfrm
EXIT
