In an earlier version of FM, I used the sum function to gather the various totals of change orders in a related file. I created a relationship for each change order and had the program match the change order numbers. Now in 7, I get nothing. I have read what I can find but there seems to be very little written on the sum function. What changed in 7?

Welcome to the Forum,

Nothing has changed with the Sum function. It sounds like you do not have a valid relationship

Shoot. Perhaps so, but I checked and renamed all 70 of relationships. I renamed them to bring more clarity between the name of fields and relationships. The sums had been working for several years in other versions. I admit I have not reached a complete comfort level with Tables but other calculations and lookups are working. I assumed it was the sum function because everything else seem to be working fine.

Without seeing the file(s), I can only guess. I assume that this is a migration from an earlier version. Have you checked the file references? Is this just one relationship where the sum function is used?

Maybe a look at a pdf of the relations graph would help.

In FM7, relationships are more sensitive to field type mismatches. There's also a possiblility that the calcs you're using for the relationship may be evaluating differently in FM7. If the field type mismatch thing isn't it, maybe you can post an example of the fields that you're using for one of these relationships (how they're defined, and what values are used.)

Also, 70 relationships sounds like a lot. There may be a better structure.

I will make a pdf of the relationship graph tomorrow when I go into work. I work on Windows XP at my day job and Mac Panther in my business. This particular file is a monthly construction pay application that can have up to 50 or 60 change orders beyond the basic contract during a job. This particular file is like a culmination of several other files starting with daily reports that superintendents fill out each morning. They have been built over a 7 year period for a small company. Thank you for your interest and help.

I'm sure you are correct on the structure. I think the term is wing and a prayer that describes the patchwork I string together. There are probably more that 70 relationships because I am having to relate each change order number to more than one file. There is a pay core and a change order base besides the pay application file. I have yet to comprehend totally having more than one table in a file. I have used file reference to bring in other files into the tables though.

Here is the pdf of the relations chart. I hope this helps

No, it wasn't. Maybe now.

Pay_App.pdf

The relations chart raises questions about the structure but it does not give a clue why the sum fuction is not working. You are aware the the relations between the COB tables and the Pay App table only work in one direction from the COB to Pay App, not from Pay App to COB.

We still don't know what type of fields your relationships are matching on. I'm guessing the CO_Num fields are globals or unstored calcs, because they have a T on that side of the relationship. As Ralph said, you would not be able to use that on the match side of a relationship.

Perhaps you should tell us what this part of the database is supposed to do. We may be able to offer a better structure that would solve your problem and simplify your relationship graph.