It happens on all machines! This form was not migrated from DOS, it was
created in Rbase for Windows. Since I never use the ascii 152
character, is there some cool way of changing the data in the Rbase.cfg
files to make it print a blank instead of � (ascii 152)?? Setting the
field to null in advance won't help if it is happening as a result of
adding a new row within the tier. The problem is not serious, but it is
hard to explain it to my customers....and it looks bad!!
Mike Sinclair
RBTI Customer Support wrote:
>
> Mike;
>
> Search the machine in question for old rbase.ini and rbase.cfg files.
> Make sure to search "My Computer" in the "Look In" line of the
> Find Dialog Box so that Windows searches ALL network drives and
> devices in your path. Rename any rbase.cfg files that you find so
> that R:BASE 2000 will create a new one. Also, make sure that there
> is only one rbase.ini file, and it resides in the default install directory
> with the R:BASE executable. The lines in the rbase.ini file that
> direct it to the HELP, MESSAGE, and CFG Paths must be correct.
>
> If this is only happening on this one machine, as per your message
> below, I would bet that you are inadvertently using the wrong
> rbase.cfg file.
>
> If this is happening on more than one machine, then it could be
> another problem.
>
> RBTI CUSTOMER SUPPORT
>
> At 10:32 AM 5/25/01, you wrote:
> >The expressions are..
> >
> >patnumbr = .vpnum (real)
> >rdate_ = .vdate (date)
> >chiefcomp = chiefcomp IN newcc WHERE shortcut = shortcut OR
> > chiefcomp CONTAINS shortcut (text)
> >
> >Browsing the table directly shows some of the values in the shorcut
> >column to be -0-, all other fields are filled with expected values.
> >The problem occurs when I am using the form, but it appears to be a
> >"cosmetic" problem...the data appears ok. In fact, if I use the form
> >to edit data on one machine, and leave the yyyyy in place, and then go
> >to another machine on the same LAN and look at the table data directly,
> >the
> >field that has the yyyyy in the form appears as -0- on the second
> >machine.
> >Further, if I go back to the first machine, and the cursor is the field
> >with good data (shortcut), and the yyyyy is in 2nd field (where it is
> >supposed to be blank), and I then hit F7 to go up one line, the bad
> >field
> >with the yyyy fixes itself (disappear/turns into a blank)!
> >
> >Any thoughts???
> >
> >Mike Sinclair
