lookup wizard malfunction?

[Fairlight]

In the relative spacial/temporal region of
Thu, May 31, 2007 at 02:27:15PM -0400, Kenneth Brody achieved the spontaneous
generation of the following:
> Quoting Fairlight (Thu, 31 May 2007 13:28:40 -0400):
> 
> > Is it just a fluke, or is it by design that in the lookup wizard, only
> > the first two indexes on the file being looked up are available via F6
> > browsing for an index?  Because that's what's happening.  The third is
> > definitely there in dxmaint, but not in the cabe wizard--even after a
> > restart of cabe.
> >
> > 5.0.14DN9, Windows 2003 Server
> 
> I can't duplicate.  Is this any file, any lookup?  Or just this one
> particular lookup?

One particular lookup, yesterday.  Here's the environment I'm working with:

F:\>type mark.bat

@echo off
rem This File created by install shield on 2-8-2006
set PFDSK=f
set PFDATA=f:
set PFPROG=f:
set PFDIR=
set PFMENU=f:\FP\MENUS
set PFGLOB=
set PFCONFIG=

set PATH=%pfprog%;%PFPROG%\fp;%PFPROG\fp\lib;%path%
%pfprog%\fp\p.exe


No qualifiers are being used or attempting to be used.  I don't actually
"do" qualifiers (or haven't to date).

That said, to answer the question about what I mean by "restarting" rcabe,
I mean that I would exit out of rcabe entirely, out to p.exe (ie.,
runmenu), then select Define Processing again.  I did this multiple times
last night.  Steps I tried:

0) I had two windows up...one in rcabe, the other sitting at runmenu.

1) I tried adding an index from the runmenu->dxmaint while I sat in
processing in rcabe's window.  Tried just repeating the F6 for the lookup
index list.  The new index (C) did not appear.

2) I tried backing out of the lookup wizard and going into the lookup
wizard again from scratch, thinking it might cache it when it is initially
started (the wizard).  Again, the C index did not appear at the appropriate
time.

3) I tried backing all the way out of the processing table and going back
in, same result as #2.

4) I tried backing all the way out of rcabe entirely to runmenu to the same
effect.

Interestingly, it would -take- index C (ie., accept it), it just wouldn't
display it as a choice no matter what I did.  I came close to step 5,
drawing runes on my monitor in goat's blood, but it seems a waste of a
perfectly good monitor. *grin* No syntax failure on save, for instance.  (I
think it's supposed to throw a syntax error on check when saving if the
index is non-existent, yes?)

I just tried now in the same table with the same lookup, and with another
lookup called "test".  This is on a different RDP session from a different
computer, as I had to relocate for the evening, but it's using the exact
same environment on the exact same account (the batch file that throws me
into runmenu has not changed one byte) as last night--and now it works
fine.  The index showed up in both tests.

Permissions never should have been a factor; I'm logged in as administrator.

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.

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