Can anyone throw some light on this problem?

I have a simple table of addresses, linked to a person table. There are two auto-enter by calc fields. One is Line1 & Line2; the other is Suburb & State & Postcode. Really complex stuff. Both have 'do not update' unflagged. Both have do not calc if all empty. The basic fields are entered in a portal when new people are added. Recently, for a new batch of people, these calcs have stopped working on initial entry - but only for some people. On my system, if I change the Suburb, for instance, the calc works. At first glance, it looks as though the Address records in the portal are not being committed - ever!

My customer is using V8.5 (on WIN XP) but, recently, I upgraded to V10 (on Win 7) In theory, this should be irrelevant but I can't help wondering.

If your fields are indeed named as you typed them in your post, then FM Help states ...

[color:blue]Field names must be unique, and can contain up to 100 characters. Follow these guidelines when naming fields:

Do not use any of the following symbols and words in the field name:

,(comma), +, -, *, /, ^, &, =, ≠, >, <, ( ), [ ], { }, ", ; (semicolon), : (colon), :: (relational indicator), $ (variable indicator)

• AND, OR, NOT, XOR, TRUE, FALSE, or the name of any FileMaker Pro function

• Don't begin a field name to be used in a calculation formula with a space, period (.), or number.

• Use _ (underscore) in place of a space to avoid restrictions in ODBC, exporting, web publishing, and other operations.

• If you're exchanging data with another application, check the field naming restrictions in the file formats supported by that application.

• If you're using ODBC or JDBC to share FileMaker Pro data, avoid using SQL keywords in field names.

Maybe it's causing or contributing to the problem.

Thanks, Iawaid. You had me worried for a moment. My field names are all fine. I'm guessing you objected to the '&'s. My 'Field1 & Field2' referred to the calculation. My fields are Field1 and Field2.