Jump to content

Crossed Information Lookup Problem


Strouss

This topic is 6113 days old. Please don't post here. Open a new topic instead.

Recommended Posts

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 by Guest
Link to comment
Share on other sites

This topic is 6113 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.