Why is this record relating to another record?????

[laker_42]

I have a workstations database and a peripherals database. The relationship is based on a computer serial # which is a text field. I have 2 workstations that have the following serial #'s: YM339WNQNVS & YM339WFLNVS. As you can see, these are not the same serial #'s. I have a portal in the workstations database that allows users to assign peripherals to a workstation. When we assign a peripheral to the first serial #, it also shows up in the portal for the second serial #. To troubleshoot this, I started deleted characters off the end of the second serial number. I got all the way down to YM33 before the peripheral no longer showed up for the second workstation. I have used this same method for other databases and have never had FMP only use the first 4 characters to determine a relationship. Any ideas why this is occurring? It has me baffled. If you could help me out, I would appreciate it!

Thanks!

John

[Ugo DI LUCA]

Hi and welcome.

I'd suggest you take a second look to how your portal is defined and what fields inside you dropped. Do they belong to this portal relationship ?

If not, I'm baffed too, as it shouldn't happen for sure. May be a corruption of some sort then.

[Ender]

My guess is the index for the Serial # field is corrupt or incomplete. Try turning off indexing, close the Define Fields dialog, then turn indexing back on.

Ugo: Is that what you look like? Didn't realize you were so young! Nice photo.

[laker_42]

Thanks for all the suggestions. I did try turning off the index and then turning it back on and it still had the same behavior. Before I posted this, I had checked the field type of the serial # in the workstations database but not in the peripherals. I just checked the serial # in the peripherals database and for some reason it was a number field type. So it was only evaluating the numbers in the serial #'s. Mystery solved! Chock it up once again to an oversight! Thanks again for the help.

John