Well, perhaps 'bug' is not the correct term. Perhaps 'poor usability design' would be more appropriate. Kind of like putting a steering wheel in a car, but not have that be the real way to drive the car.
When I ask to search on a given field, it is the job of a well written program to do that, or to explain why it can not. It asks for a value, and seems to correctly accept the value. I stayed up 'til 1am working on this last night, and my head is now in a fog. I'll have to think about this more later when I can see straight. :-) Thanks all Kevin --- steven mcphelan <[EMAIL PROTECTED]> wrote: > I would not call this a bug. I suspect that Fileman > is doing everything > properly. However, because of the Output Transform > on field 1302, this > causes Fileman to fail to find the matches. By > putting an output transform > on a pointer field you are asking FM to lookup a .01 > field value in the > pointed to file. Yet FM will compare that value > with the value from field > 1302 which has the output transform on it to display > the INITIAL field from > the NEW PERSON file. Obviously, the person's name > does not equal the > person's initials and thus no matches are found. > > One can manipulate a file's data structure so that > it will cause the generic > Fileman tools to apparently misbehave. So who is at > fault, if even there is > anyone at fault? Is generic Fileman at fault or is > the owner of file 8925 > at fault? In this case, I do not think either one > is at fault. I have > always said, one cannot look at the Data Dictionary > of a file and expect to > know all the related business rules regarding that > file. You are trying to > bypass those business rules by going to the native > data structure to extract > data using generic Fileman. Many VistA files are > not truly Fileman > compatible. By this, I define Fileman compatible as > entering data via > generic Fileman tools into a file being exactly > equivalent to entering that > same data through the supported package interface > and honoring all business > rules for the entering of that data. > > ----- Original Message ----- > From: "Greg Woodhouse" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Sunday, March 20, 2005 10:46 AM > Subject: Re: [Hardhats-members] Another example of > Fileman Search being > unreliable > > > > 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: <[email protected]> > > > > 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: > <[email protected]> > > > > >> 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, === 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 [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
