lookup wizard malfunction?

[Fairlight]

Only Jay Ashworth would say something like:
> On Thu, May 31, 2007 at 05:08:58PM -0400, Fairlight wrote:
> > I can't reproduce it now, but I could reproduce it in all four of those
> > scenarios last night.  That's about the best I can tell you folks.  I'll
> > chalk it up to Demo Syndrome if I have to.  But it -wasn't- acting right at
> > the time or I'd not have asked about it.
> 
> You haven't rebuilt any of those indexes between doesn't-work and
> works, right?

Actually, I went back and verified that it existed in dxmaint several times
between the steps listed before.  I did not do a "rebuild" unless selecting
automatic processing, selecting index C, and hitting enter to get to the
length field, and hitting escape to save out again counts, which I kinda
doubt it does.  I was just trying to see if there was something wrong with
its definition, honestly.

I'm not on the system right now and only have time for a quick note, but
I'd have to actually look at the menus and/or docs to find out how to
rebuild the whole index intentionally.  I've never needed to before, to be
honest.  Define it and it just works usually.

That's -exactly- all I did, however, FWIW, was check the definition with
dxmaint and hit escape (rather than break out).   I should mention that
cabe's behaviour did not change after having done that.  It only differed
today when I was on an entirely different RDP session, not having touched
fP in any way between those two time frames, much less any of the affected
files.

mark->
-- 
No matter what your problems, modern medicine can help!
http://members.iglou.com/fairlite/fixital/