Serial number +1 duplicate

[Michelle Logan]

Not sure if this is the correct location or not.

 

We have a field called "Record_Number_Alt", this is nothing more than a serial number plus 1 that we reference on a couple of searches.

 

Last week we had a record created and the number was set in place (lets call the number 99500), other records were created throug the week and all increased by 1 up to 99555.

 

A new record was created this week that had the old serial number of 99500 (the number from a record last week), even though the next field number was showing it was set to be to be 99556, and all records to date have had the number set correctly +1.

 

Has anyone ever seen this issue or have an idea as to what caused it? The number is set to be unique etc. etc.

 

Note: The Primary Keys for all the records are correct and have not been duplicated.

 

Thanks,

 

Michelle

[Ocean West]

is that field Editable in any layout in browse mode? Perhaps someone was thinking they were searching and were in browse, and overwrote the value.

[comment]

I don't understand your description.

 

We have a field called "Record_Number_Alt", this is nothing more than a serial number plus 1

 

Is this a calculation field? And what exactly is the "serial number" - is it a field? And most importantly, was there a problem with the serial number itself or only with the Record_Number_Alt field?

[Michelle Logan]

Hi,

 

Sorry for the confusion.

 

The field is just a number field (no users can access it) we just use it as a secondary reference on a search.

 

 

In the options for this field:

 

Auto-Enter tab: Serial Number / Generate on Creation / increment by 1

 

Validation Tab: Require: Unique Value

[Wim Decorte]

This can happen if:

- someone went back to a backup of the file and imported the old data but forgot to reset the serial #

- someone manually changed the field options, or a script uses the "set next serial" for that field

[LaRetta]

Another possibility is that Users are accidentally accessing an older copy of the file.

[Josh Ormond]

Is the 'Replace Field Contents' feature available to the users? That can also update the serial number for a field.

[Michelle Logan]

Thanks for all the replies.

 

I have read each one carefully and none relate to this issue.

 

The field is not accessible to the user.

They only have access to the current server hosted file, the backups are kept on a secondary drive.

All users are locked out of access to everything by custom menus and scripts. Anything they do is scripted via a button (Create, Exit etc.).

 

The strange part is that there were records created up to the number I posted, there were records created after the number, and all were fine. Then just out of the blue, the same number appears 25 records later. Then all records after the duplication were correct (the number +1).

 

There around 800 student records in this DB, and there has never been an issue with this Number Field. We have searched for other duplicates and have found none.

 

Thanks,

 

M.L.

[bruceR]

I am curious how this field  provides practical value to you. "Secondary reference on a search". Could you explain that?

[Ocean West]

Ok I have run in to this before.

 

If you were modifying the SCHEMA and had uncommitted changes to the schema of the file at the same time someone was running a script the script fails fmp client will NOT create the new record but inject data into any existing record (overwriting data)

 

In order to prevent issues is to NOT modify schema during working hours or you need to add logic to your scripts to trap for errors and when it fails present the user with appropriate error.

[Michelle Logan]

Ok I have run in to this before.

 

If you were modifying the SCHEMA and had uncommitted changes to the schema of the file at the same time someone was running a script the script fails fmp client will NOT create the new record but inject data into any existing record (overwriting data)

 

In order to prevent issues is to NOT modify schema during working hours or you need to add logic to your scripts to trap for errors and when it fails present the user with appropriate error.

 

This could very well be the cause.