<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2743.600" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Courier>Today I came across something I did not
know.</FONT></DIV>
<DIV><FONT face=Courier>I have a zip code file of US and Canadian zips in a
filePro database. Index A is build on the zip code field and the city
field.</FONT></DIV>
<DIV><FONT face=Courier>I'm doing a lookup into it using the zip code
only. If I find a match, I do a getnext and if it is the same zip code but
to a different city, I display a browse window with all the cities matching the
zip code, for the user to choose from. This works fine.</FONT></DIV>
<DIV><FONT face=Courier></FONT> </DIV>
<DIV><FONT face=Courier>However, if there is already something in the city and
zip code fields, I wanted to display the same browse window but with the
highlight on the record matching the city. To acomplish this I was
stuffing a dummy field with the contents of the zip & city fields like:
</FONT><FONT face=Courier>ky=77&75</FONT></DIV>
<DIV><FONT face=Courier>and doing the lookup. In order not to display zip
codes that did not match, I put a match length of 7 (the length of the zip code
field) in the browse lookup. To my surprise, the highlight always falls on
the first record of the browse window, even though doing an errorbox of the ky
dummy just prior to the lookup, shows that it contains the zip code and
city. Changing the position of the first record to middle or bottom has no
effect, the highlight bar is always on the first record matching the zip
code. Is this because I put a match length of 7 on the lookup or should it
work the way I thought it would?</FONT></DIV></BODY></HTML>