Auto enter failure

[Rick Whitelaw]

Hi,

I have a parent table called Subs Table and this table has three child tables, Sub1 data, Sub 2 data and Sub 3 data. Each of these child tables has a field "Year" defined as a number field with auto enter Year(Production Info::Payday). The layout based on the parent has three one-line portals. One for each child table. Each child table has identical relationships to the parent. The Year field works fine on the second and third child tables, but not in the case of Sub 1data. Oddly, if I delete the portal row (related record) and re-enter the data, it does work! Also, Production Info table is far removed but with proper relationship chain, and the auto-enter does work in the other two child tables. I'm beginning to suspect corruption. One more thing: if I create another TO of Production Info and relate it directly to Sub 1 data, the auto enter works. I shouldn't have to do this.

[Rick Whitelaw]

Figured it out! I'll share before anyone replies. It was so simple I'm embarrassed. I must have been in the habit of, after a script created a new blank record, of filling in the one field needed on the parent part of the layout then clicking elsewhere on the layout, thus committing the parent record. Lately I had taken to filling in the field then tabbing to the portal fields. The Year field in the child table wasn't filing because the parent hadn't been committe and a record was necessary to create the relationship to the table containing the Date field "Payday". Doh! I attached an OnObjectExit one line script to the first data field (parent) which is simply Commit Record. Problem solved. Interesting . . . I wasn't even aware of my data entry habits on this layout. Of course, the second and third child tables didn't exhibit the same behavior because once I got to those, there WAS a committed parent record. I've used this layout for years . .

[Rick Whitelaw]

Hmm . . . Now I understand why posters often have their own answer marked as "best answer". I marked my own reply as "solved" and all of a sudden it's marked as Best Answer which I've always considered a breach of etiquette. Now I know why it happens.