Hey Mr. R:>

How could this be an installer? I installed RBase Win6.1a from 
a Win98 machine onto the Novell network server a long time ago -- 
well when we bought it from RBTI... It's never been changed and
has worked like a charm for a long time now. 

The only thing I have done is to copy a shortcut straight from the
network and then put the parameters we use on the Target line of
the shortcut like: K:\rbwin\RBG.EXE -oc:\rbw61\rbase.cfg -r
This system of copying shortcuts to the EXE works on all W2000 
systems throughout the building except for the two ladies having
this error. Well, the other W2000 machines are on another server -- 
which is not the server rbase is on. The server Rbase is on is 
the one that these two ladies log into as their primary server.
One of these ladies is our system administrator, so I know it's 
not a access thing. She has access to everything.

Just thought of something though. Could it be RBase.INI file?
There is only one in the K:\RBWIN directory.

Still diggin in
Jim Limburg


"A. Razzak Memon" wrote:
> 
> At 10:49 AM 7/31/2001 -0400, Jim Limburg wrote:
> 
> >One of the big questions here is why would RBase even
> >look at this file one some machines an not others.
> >Would it be the Client that is telling it to look for
> >this?
> >
> >Any help appreciated on this one
> 
> Jim,
> 
> That is the result of using three year old software
> installer running on Windows 2000!
> 
> The Glorious R:BASE 2000 (ver 6.5) and especially the
> 6.5++ uses the latest windows installer to be compatible
> with Windows 2000!
> 
> Cheers,
> 
> Razzak.
> 
> ===================================-============================
> R:BASE Developers's Conference: http://www.rbase.com/conference
> 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.
> ==================================-=============================

Reply via email to