Jump to content

relational graph for scheduling conflicts


Reed
 Share

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

Recommended Posts

I'm starting on a solution to schedule the use of resources in our lab. Ive attached a file which attempts to use relationships and a calculation field to detect scheduling conflicts. This appears to work, but I'm looking for input on whether this is the best approach to use.

Also, I'm looking for a way to use field validation to disallow commiting a record if it conflicts with an existing record. Any ideas on how to validate this w/o the use of a script?

FileMaker Version: Dev 7

Platform: Mac OS X Panther

schedule.zip

Link to comment
Share on other sites

Reed,

Your relationships to test for conflicts seems like a very good design to me, I don't see how it can be done better without an OR in the relationship creator.

For the validation, I added a validation calc on the "id" field:

conflict = 0

then turned off the "Validate only if field was modified" option in the calc dialog.

Turn off "allow override" and add a nasty custom message and you're there with no script.

Link to comment
Share on other sites

I tried this validation technique as well, but it seems that the validation is based on the count() functions prior to record commitment. So it doesn't catch a conflitct if there is only one. If you change the condition to count>0 instead of >1 then it works, but if you try to edit the record, it conflicts with itself. Any thoughts on how to get around this? (Again, without the user have to execute a script.)

Dana

Link to comment
Share on other sites

This topic is 6477 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
 Share

×
×
  • Create New...

Important Information

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