Oh.....  you are talking about the dialog to set up the search...  sorry.

Greg Woodhouse wrote:
That was my understanding, but consider thhat the basic symptom is that
we are comparing a pointer field for equality after doing a lookup
(selection after entering the '=' condition), but Fileman fails to find
a value when entering one lookup value ("kst"), but it does succeed
when entering the .01 value.

I'm not suggesting that the SEARCH uses and index, but that the user
dialog makes use of an index when looking up a pointer value for
comparision purposes. I'll have to try it out under another scenario
and see if this occurs consistently.

--- Greg Kreis <[EMAIL PROTECTED]> wrote:

  
The A, B, C conditions don't use an index.  They are 'if' statements 
that are applied to records that are found by the SORT BY part of the

Search.  Now, depending on how the SORT BY is constructed, it can use
an 
index or simply order through all the records of the file in record
order.

Kevin Toppenberg wrote:

    
Is the search dependant on an index?  What if I were
to define a file that did not have an index.  Would it
not be searchable?  I thought it was sweeping through
all records in the given file.

Regarding the DIC("PTRIX"), surely the end user is not
expected to do this...(?)

Thanks
Kevin

--- Greg Woodhouse <[EMAIL PROTECTED]> wrote:

 

      
My guess is that Fileman in looking in the "B"
cross-reference for
"kst" and not finding it. When doing a DIC lookup, I
think you need to
set DIC("PTRIX") (I'm going by memory) if you want
to look up a
"pointed to" value using a different index.

--- Greg Woodhouse <[EMAIL PROTECTED]> wrote:

   

        
It would still be interesting to know if the
     

          
search fails when
   

        
entereing "TOPPENBERG, KEVIN" instead of "kst".


--- Lloyd Milligan <[EMAIL PROTECTED]> wrote:

     

          
Something about the ENTERED BY field DD seems to
       

            
prevent the search
   

        
>from 
          
working as expected.  As you pointed out,
       

            
initials are a valid
   

        
lookup
     

          
value. 
So why doesn't this work?

Lloyd

----- Original Message ----- 
From: "Kevin Toppenberg" <[EMAIL PROTECTED]>
To: <hardhats-members@lists.sourceforge.net>
Sent: Sunday, March 20, 2005 8:33 AM
Subject: Re: [Hardhats-members] Another example
       

            
of Fileman Search
   

        
being 
unreliable


       

            
Ok, that does work.

But as far as I am concerned, THIS IS A BUG!

Any reasonable user (and seasoned Fileman
         

              
users on
   

        
this board) can't figure this out.

Kevin

--- Lloyd Milligan <[EMAIL PROTECTED]>
         

              
wrote:
   

        
This has something to do with initials being
           

                
an
   

        
output transform.  If you
use INTERNAL(ENTERED BY), EQUALS, 73 it
           

                
should work.
   

        
Lloyd

----- Original Message ----- 
From: "Kevin Toppenberg" <[EMAIL PROTECTED]>
To: <hardhats-members@lists.sourceforge.net>
Sent: Sunday, March 20, 2005 7:59 AM
Subject: Re: [Hardhats-members] Another
           

                
example of
   

        
Fileman Search being
unreliable


           

                
Still doesn't work.

I went back to that particular record, and
             

                  
reentered
           

                
value for ENTERED BY field.  I entered
             

                  
'kst', and
   

        
it
           

                
expanded to 'TOPPENBERG, KEVIN S' (By the
             

                  
way,
   

        
kst's
           

                
DUZ=73)

I then looked at the data with VPE's VGL
             

                  
function.
   

        
Here it is.  You can see that node;piece
             

                  
13;2
   

        
(field
           

                
1302=ENTERED BY) here = 73  (Also, I looked
             

                  
at the
   

        
global data for other documents that I had
             

                  
not
   

        
re-entered, and they also were 73.)

==================================[Session
1]==================================
1) ^TIU(8925,4299,0) =
1305^34245^^^7^^3041105^3041105^^18
2) ^TIU(8925,4299,12) =
3050207.210339^74^^74^11^^^^74^^11
3) ^TIU(8925,4299,13) = 3041105^73^U
4) ^TIU(8925,4299,14) = ^^^3
5) ^TIU(8925,4299,15) = ^74
6) ^TIU(8925,4299,"TEXT",0) =
             

                  
^^27^27^3050207^^
   

        
7) ^TIU(8925,4299,"TEXT",1,0) =

I then re-ran the search.  Still no
             

                  
matches.  Here
   

        
it
           

                
is:


OUTPUT FROM WHAT FILE: TIU DOCUMENT//

-A- SEARCH FOR TIU DOCUMENT FIELD: authOR
             

                  
OF NOTE
   

        
AUTHOR/DICTATOR
-A- CONDITION: =  EQUALS
-A- EQUALS NEW PERSON: ptt  THWING,PHILIP
             

                  
T
   

        
ptt
           

                
      PHYSICIAN

-B- SEARCH FOR TIU DOCUMENT FIELD: entereD
             

                  
BY
   

        
-B- CONDITION: =  EQUALS
-B- EQUALS NEW PERSON: kst 
             

                  
TOPPENBERG,KEVIN S
   

        
kst          PHYSICIAN

-C- SEARCH FOR TIU DOCUMENT FIELD:

IF: A&B    AUTHOR/DICTATOR EQUALS 74
             

                  
(THWING,PHILIP T)
           

                
               and ENTERED BY EQUALS 73
(TOPPENBERG,KEVIN S)
OR:

STORE RESULTS OF SEARCH IN TEMPLATE: [TMG
             

                  
SET
   

        
                            (Mar 20,
             

                  
[EMAIL PROTECTED]:09)
   

        
User #73 File #8925   SEARCH


DATA ALREADY STORED THERE....OK TO PURGE?
             

                  
NO// y
   

        
YES
           

                
DESCRIPTION:
This can be used to store sets of records,
             

                  
for
   

        
working
           

                
with multiple
records etc.

Edit? NO//

SORT BY: NUMBER//
START WITH NUMBER: FIRST//
FIRST PRINT FIELD: .01  DOCUMENT TYPE
THEN PRINT FIELD:
Heading (S/C): TIU DOCUMENT SEARCH//
DEVICE:   TELNET
TIU DOCUMENT SEARCH                        
             

                  
  MAR
   

        
20,2005  07:34    PAGE 1
DOCUMENT TYPE

             

                  
--------------------------------------------------------------------------------
    
 

      
                       0 MATCHES FOUND.







Thanks

Kevin



--- Floyd Dennis <[EMAIL PROTECTED]>
             

                  
wrote:
   

        
The problem appears to be with your data,
               

                    
not
   

        
with
           

                
FileMan.

Look at the ENTERED BY field in your
               

                    
record 4299.
   

        
If it were reflecting a
               

                    
=== message truncated ===



		
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real
      
users.
    
Discover which products truly live up to the hype. Start reading
      
now.
    
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members

 

      
-- 
Greg Kreis      http://www.PioneerDataSys.com

"You are today where your thoughts have brought you, you will
   be tomorrow where your thoughts take you." (James Lane Allen)


    

A practical man is a man who practices the errors of his forefathers. --Benjamin Disraeli
====
Greg Woodhouse 
[EMAIL PROTECTED] 
[EMAIL PROTECTED] 





-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members

  

Reply via email to