Odd Relationship Problem...

[asevie]

I have a relationship that intermittently displays the appropriate related information. As I was troubleshooting this, I renamed the relationship and, even though the new name carried thru to the appropriate fields, the relationship stopped working. So I backtracked thru and checked each piece, to no avail. Even when I renamed the relationship back to the original name, it continued to work incorrectly. I resorted to a backup and continued adding additional days, when, suddenly, it stopped working again.

Any ideas why this calculation, based on different relationships would not work? The field in question simply determines the start time of the shift the record represents.

Case (

Day="MO" and Shift="L"; Lot Mon AM::MO_L_Start;

Day="MO" and Shift="D"; Lot Mon PM::MO_D_Start;

Day="TU" and Shift="L"; Lot Tue AM::TU_L_Start;

Day="TU" and Shift="D"; Lot Tue PM::TU_D_Start;

etc...

"" )

Simply put, the LOT table holds the start and stop times for each shift, Lunch and Dinner, for each day of the week for each account, or LOT. There are 14 shifts in a week for each record in LOT.

In the table called SCHEDULE, each record holds the individual working the shift, with a start and a stop time. The related field looks something like 1-TU-L. (1 being the LOT ID, TU being the Day and L or D meaning Lunch or Dinner.) In LOT, these are each hard coded in an individual field.

One shift in LOT may have multiple people in SCHEDULE working it. The SCHEDULE table is made up of all the people working all the shifts at a certain LOT thru out the week.

[Vaughan]

It could be a number of things.

Data corruption: save a compressed copy of the file, import the data and see if that fixes it.

Field type mismatch: make sure the fields on both sides of the relationships have the same data type.

[asevie]

Data corruption: save a compressed copy of the file, import the data and see if that fixes it.

Field type mismatch: make sure the fields on both sides of the relationships have the same data type.

I hadn't thought about the first suggestion and I thought perhaps that might work, but, no luck.

I have retraced each field on both sides and they are all correct. The odd part is that given two values on both sides, ex. 1-TU-L, I cannot 'see' anything thru the relationship.

Thanks for the ideas, I was really hoping it would be some little FileMaker quirk...

[asevie]

And it just gets more strange. I duplicated the field, stipped almost everything out, saved, opened Field Defs again and pasted the original back in, and it works. Oh, well, it's working I can't complain.