Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×
The Claris Museum: The Vault of FileMaker Antiquities at Claris Engage 2025! ×

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

Recommended Posts

Posted

I have two databases, USER and CPU, related to each other using a field called CPUID.

Here's the basic setup. USER database holds user info(last name, first name, etc.) while CPU databse holds cpu info(Model, speed, etc.). Each CPU record has a unique number which is stored in CPUID field. This is good and works fine. In the USER db I also created a CPUID field which I'm using to connect a user record to a cpu record. So the relationship is from CPUID to CPUID both ways.

From the USER db, I go to the user record I want, then enter the unique number for the cpu record I want in the CPUID field, bringing up the information for the related record. In this way I assign a computer to a user. I hope this makes sense, I strugle with db terminology.

Here's my issue. I want to restrict the ability to assign any CPU record(CPUID number) to more then one USER record. Meaning, two users cannot have the same cpu.

is there any way to have fmp check to see if the number I'm entering in CPUID(which is a related field) have been entered before in the users db?

I hoep that makes sense. .if it doesnt pleae diect we where to clarify.

Thanks in advance,

Steve S

Posted

You could also do a verification that checks to make sure the data is unique. ITs a simple checkbox. Then, it'll just yell at you if you enter a non-unique code.

This topic is 8002 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.