Thanks for the prompt reply.
At 23:57 17/04/01 -0400, you wrote:
>Using The Glorious R:BASE 2000 (ver 6.5+) or higher:
>CONNECT D:dbname READ IDENTIFIED BY userid password
>Where D: is the drive letter of your CD-ROM drive.
Sorry if the following rambles, I've been up since 4:00am...
The specification is for the database to be run solely from the CD - no
installation
to the host computer and to be very user friendly to computer illiterates.
If the CD is to be distributed to dozens of users and the drive letter of
the CD is
not only not known but can vary from one user to another, can the rbase.ini
file
specify the message file without a drive letter if the R:Base runtime files
as well
as the database and application files are all in the root directory of the CD?
Eg. the rbase.ini file currently holds required data in the format:
[R:BASE]
RecentFile5=F:\DevMach1\RB65\BizMan\COMPARE.RB1
RecentFile4=F:\DevMach1\RB65\BizMan\Tester.RB1
RecentFile3=F:\DevMach1\RB65\BizMan\BizMan.RB1
RecentFile2=F:\DevMach1\RB65\BizMan\TomsData.RB1
RecentFile1=F:\DevMach1\RB65\BizMan\TomsData.RB4
SYS_RES_THRESHOLD=15
MSGPath=C:\RB65W\RBWIN65
HelpPath=C:\RB65W\RBWIN65
CFGFile=C:\RB65W\RBWIN65\RBASE.CFG
As the drive letter will vary from one machine to another, is it acceptable
to have:
MSGPath=
HelpPath=
CFGFile=RBASE.CFG
or
MSGPath=(CVAL(''CURRDRV')
HelpPath=(CVAL('CURRDRV')
CFGFile=RBASE.CFG
or in rbase.dat
SET VAR vDrive TEXT = (CVAL(''CURRDRV')
SET VAR vCfgStatement TEXT = (.vDrive + '\RBASE.CFG')
then
MSGPath=&vDrive
HelpPath=&vDrive
CFGFile=&vConfigStatement
or (someone told me the following practice was not strictly kosher for
ampersand variables even though I use it fairly frequently)
or in rbase.dat
SET VAR vDrive TEXT = (CVAL('CURRDRV')
SET VAR vCfgStatement TEXT = (.vDrive + '\RBASE.CFG')
SET VAR vMsgPath TEXT = ('MSGPath=' + .vDrive)
SET VAR vHelpPath TEXT = ('HelpPath=' + .vDrive)
SET VAR vCfgFile TEXT = ('CFGFile=' + .vDrive + '\RBASE.CFG')
then in rbase.ini
&vMsgPath
&vHelpPath
&vCfgFile
If not, is there a way to have a dynamic reference to various rbase.ini
files with
different names, such as:
rbase_d.ini for the D drive
rbase_e.ini for the E drive
etc.
Any other bright ideas?
>Enjoy and make sure to have fun!
>
>Very Best Regards,
>
>Razzak.
>
>At 01:03 PM 4/18/01 +1000, Tom Grimshaw wrote:
>
> >Because R:Base updates the RB1-4 file date/time stamps
> >when a database is accessed one cannot run an R:Base
> >database resident on a read only CD, can one?
>
>
>===================================-============================
>Official R:BASE List Server: mailto:[EMAIL PROTECTED]
>RBTI Events/Training: http://www.rbase2000.com/events
>R:DCC Members: http://www.rbase2000.com/rdcc
>================================================================
>R:BASE, Oterro & R:Tango are registered trademarks of RBTI.
>==================================-=============================
Warmest regards,
Tom Grimshaw
coy: Just For You Software
tel: 61 (0)2 9552 3311
fax: 61 (0)2 9566 2164
email: [EMAIL PROTECTED]
mobile: 0414 675 903
street: 3/66 Wentworth Park Rd Glebe NSW 2037
post: PO Box 470 Glebe NSW 2037 Australia
_/_/_/_/_/_/_/_/ _/_/_/_/_/_/ _/ _/ _/_/_/_/_/
_/ _/ _/ _/ _/
_/ _/ _/ _/ _/
_/ _/_/_/_/ _/ _/_/_/_/_/
_/ _/ _/ _/
_/ _/ _/ _/ _/
_/ _/ _/ _/_/_/_/_/
