Strange data loss...

[lazer]

I just experienced something very strange, hopfully any of you can explain this.

I have a separated solution with 3 files (actually 5, but only 3 involved in this example). I have a script in my interface file that creates one record in the data file, and one in the br file. The relationship between GUI and data is a global number to ID (auto-enter serial) (creation of data record allowed). The relationship between the GUI and br is the same global number field to a plain number ID field.

OK. The script goes like this:

- The GUI global number field is set to empty.

- A field in data TO is set to a value (a name field).

- Record is committed.

- Some other fields in data TO are set.

- A field in the br TO is set to a value. (With the GUI global number now populated with the data auto-enter serial).

That's about it.

Here comes the strange:

No data record was created.

BUT, br record was created with the "right" ID.

AND, calculations in br based on values in data set by the script, are showing correct!!

When I'm looking in Define database in data the auto-enter serial has "jumped" one step.

So, the br calculations relates to data that I cannot see.

Of course I have shown all records and even tried to find the record by ID. The files have never crashed as far as I know.

Has any of you experienced anything like this? I think it's really wired.

[SlimJim]

I am not familar with the separation model but your symptoms - missing data record, ID jumping by 2 sound like a record has been automatically deleted. Could this have happened via any of the relationships you have set up?

[lazer]

That was my first thought too,

but the thing is that calculation fields from another table still refering to the missing data record, and doing so correctly...

When the script creates the data record, it automaticaly enters a name in a field. This name is then styled by a calculation in the br table. And the field in the br table are showing the right name. I even deleted the br record and recreated it with the same ID, and the correct data still showed up...

'Tis quite strange, isn't it?

[SlimJim]

This is very mysterious. I have no solution to offer just more suggestions which you have probably looked at already.

Going over some of the individual bits of evidence: the calculations in your br record can still "see" the record with the missing ID. (Are br and data related by ID?) Therefore it is a fair assumption that the record exists, whether or not you recognise it. Also the fact that the missing ID number can be recreated in the br table is extremely odd; it must be there but you cannot FIND it.

Your auto-enter serial number skips a step. Evidence that two data records have been created, however, at what point is the serial number auto-entered? Is it on creation of the record or on committment of the record?. Does the count of the data records match the number of ID numbers that you can see? Is it possible that you have two data records with the same ID or even a data record with no ID?

A large number of strange problems which are being seen in FMP7 are due to the fact that records have to be committed or they do not exist, even if you can see them on the screen. It is well worthwhile looking at the committment of the two records that you are creating