Crossed Information Lookup Problem

[Strouss]

My customer database is crossing looked up data. The lookup is based on a site number text field that sometimes has a "0" on the end of the number. We have customers with multiple work sites. Our site number works like this.

"CustomerNumber.HowManySitesCalculation" So if we have 9 sites for this particular customer and we ad a site that new site is "CustomerNumber".10

I have changed from dashes to decimal points because the lookup didn't "see" the dashes.

The lookup is crossing information from site number 1143.1 to site number 1143.10 I believe it drops the last 0 in the lookup because it not numerically necessary and pulls information from the first record it finds. I changed the field from a number to a text field with no improvement.

My crew showed up at Archstone San Jose to do what they were supposed to do at Archstone Walnut Grove.

Is there any way to get filemaker to recognize the 0 on the end. Would a different type of field work better?

Edited September 27, 2007 by Guest