grumbachr Posted April 2, 2007 Posted April 2, 2007 I've tried several things that I could think of but with no luck. I'm turning to you good people for some help. Here in my example I have 2 tables Contacts and Contact Details. Each contact can have many ways to be contacted but I want them to only have one main contact. How can I keep people from having more than one? I tried to validate by a calculation but no calculation I made would work. If you have any suggestion they are greatly appreciated. one_main.fp7.zip
sbg2 Posted April 2, 2007 Posted April 2, 2007 Attached is what I came up with using: - a seperate table for storing the Maincheck - 2 new table occurences. - a button to run a script under the checkbox z_one_main_rev.zip
grumbachr Posted April 2, 2007 Author Posted April 2, 2007 Thank you very much. That works. I'm still trying to understand the logic but you found a solution to my problem. thanks again.
grumbachr Posted April 3, 2007 Author Posted April 3, 2007 thank you too. i always find it intesting how different people find a way to resolve the same problem. I've learned from both of you and that is appreciated.
sbg2 Posted April 3, 2007 Posted April 3, 2007 the cMainCheck = Detail_ID = Contacts::MainDetailID through me for a loop until I realized it was a true/false result. Thanks for that simple sample. When adding a new record the checkbox will not show as checked until I click outside the portal. Does this happen to anyone else or just me?
comment Posted April 3, 2007 Posted April 3, 2007 The calculation will not evaluate on a non-committed record. Try it this way. one_main.fp7.zip
Recommended Posts
This topic is 6505 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 accountSign in
Already have an account? Sign in here.
Sign In Now