-RO causes an error

[Joe Chasan]

On Fri, Jun 03, 2005 at 12:38:06PM -0400, Joe Chasan wrote:
> On Fri, Jun 03, 2005 at 12:16:53PM -0400, Kenneth Brody wrote:
> > Quoting Joe Chasan (Fri, 3 Jun 2005 12:10:57 -0400):
> > [...]
> > > the workaround in my case was to add a second field to index "A" in
> > > MY_FILE_NAME, even though index was already unique, to force filepro
> > > to use new 4.5/4.8/5.0 multi-field index format internally within
> > > that index.
> > 
> > Or just don't set PFOLDIX=ON, and filePro will use the new format
> > even for single-key indexes.  (Unless there is a need to use the old
> > format for some reason.)
> 
> ken, in my case PFOLDIX wasn't set at all, so i'm not sure why index
> was in older format.  FWIW, index was on a field of 10,mdyy/ on a 
> file of 21 records.

... and since you challenged me, Ken, i have to throw it back to you as
a second bug.

it occurred to me while lunching that the filerpro file in my case was 
never around until after customer had 5.0, and i know i'd never set 
PFOLDIX in their case - so how could it get the old-style index format?  
what's the bug?  

if an index is created in ddefine/define files, a single field one (the
only kind you can build from ddefine!), it still uses the old format.

if you rebuild it in dxmaint/index maintenance, it uses the 4.5/4.8/5.0
format.

verified in both sco unix & windows
  
-joe

--- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ---
-Joe Chasan-                      Magnatech Business Systems, Inc.
joe at magnatechonline.com           Hicksville, NY - USA
http://www.MagnatechOnline.com    Tel.(516) 931-4444/Fax.(516) 931-1264