Naomi,
Thanks for the reply.
The search is used throughout the entire system. There is a small .prg wrapper that is called like this
=l3lookup("FIEL=[M.user_input]EXPR=[status]" +;
"ALIA=[status] + TAG=[status] + ORDE=[status]", ;
"status:r:h=[]", ;
"","M.user_input","Titl=[Status]" + ;
"WROW=[12]WCOL=[12]Colo=[10]")
It allows display of 2 or more columns in a table.
The user can arrow between columns, changing the search key at the same time.
i.e. If my cursor is in the SLSMNCOD field, keystrokes trigger an incremental search on SLSMNCOD. If the user arrows over to the NAME field, the search is now on NAME field.
USMARC is the cataloging specs, published by Library of Congress for all publications.
Check out:
http://www.loc.gov/marc/bibliographic/MARC 21 Format for Bibliographic Data: Table of Contents (Network Development and MARC Standards Office, Library of Congress)
We wrote a system for a bookseller that allows him to provide MARC records and book labels with books he sells. This is a requirement for selling books to libraries.
TIA,
Dan
>Hi Dan,
>
>Welcome back!
>
>Where exactly the Incremental Search was used? If you want to use Incremental Search in Grids, there was a class called InGrid in Downloads section here
GridSearch Download #
32414>
>BTW, what is USMARC application ?
>
>
>
>>Hello all,
>>
>>It's been a while since I've been out here (2004!!).
>>
>>Nice to be back.
>>
>>We are converting an FPW2.6 application to VFP 9. For the most part, it's going real well.
>>
>>However the original programmers used a third party search routine that provided an enhanced incremental search feature whenever a table lookup was required in an input field.
>>
>>As the subject says, it is called L3SRCH and it was compiled into an L3SRCH.FLL library which, of course, VFP doesn't like.
>>
>>Though admittedly optimistic, I was wondering if anyone out there has a recompiled version of this utility for VFP 9 or a plug-in replacement?
>>
>>If not, I do have the C code and I could create an .FLL myself but I've never done that. The VFP Help mentions a way if using Visual Studio 6. I don't use that, but have it somewhere if necessary. If I have to rebuild the FLL, can someone point me to documentation?
>>
>>As a third possibility, perhaps I could just send the .C file (very small, single prog) to someone that could create a VFP9 compatible FLL for me.
>>
>>Thanks in Advance,
>>Dan