How about a command line switch where one value would make RBase look for
the startup db in the EXE dir and another that would be followed by the
actual location of the startup db like the -O switch for the CFG file, so
you could use a common db for instances when it would be appropriate.



----- Original Message -----
From: "Jim Limburg" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, November 20, 2001 3:28 PM
Subject: Re: Placement of RBASE.CFG and RBASe.INI files


> Not a Bad Idea there Mike, but what if you
> have different settings for differenct users?
>
> I know I have different users with different
> screen size settings and this would present
> some difficulties..
>
> RBTI would have to set this up for single
> capability or multi-user capabilty..
>
> Are you saying that this should be a copyable
> database that would be say named different for
> every user, or one that would hold a users settins
> in which their would have to be some kind of setup
> capabilty or ???
>
> Jim Limburg
>
> MikeB wrote:
> >
> > Here is a novel idea.  How about a small RBase database that would be
> > STANDARDIZED to contain startup paramaters and kept in the Executible
folder
> > and would be read on startup by the engine. An RBase Exclusive Registry.
> > After all, the Registry is no more than that. Just another Database.
> >
> > mike
> >
> > ----- Original Message -----
> > From: "Nicky Avery" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Tuesday, November 20, 2001 12:06 PM
> > Subject: Re: Placement of RBASE.CFG and RBASe.INI files
> >
> > >
> > > I'm sure there is a reason why we are able to specify in Preferences
> > > where RBASE.CFG lives and then have it ignored while R:Base goes out
> > > trawling every partition in sight for other vintages but I'm not sure
> > > what it is. I believe it would be more convenient if we were able to
> > > specify in R:Base's setup where to find both RBASE.CFG and RBASE.INI
and
> > > then have RBase accept the locations.
> > >
> > > I'd like to add my voice to the chorus that using the registry is a
poor
> > > idea. I am not sure I see the point of trying to produce a solid
> > > application and then making it hostage to a fragile rats' nest subject
> > > to invasion by every spyware and junkware program.
> > >
> > > $0.02
> > >
> > > Nicky
> > >
> > >
>


Reply via email to