I have a Purchase Order system that uses a serialized value to track PO records. After record creation, this number is attached to a julian date to make a po number like this: 06052012-xxxxx, where xxx is the serialized value. Everything is fine at this point. The serialized value has never had a problem making the secondary PO number.

However, when going back in to some of these records, I'm finding that the serial field sometimes reverts to 1.

I really dislike when issues are sporadic. Any body ever have this issue?

I could write a script that would parse the PO number and reassign the correct serial, but that will not help

this from happening in the future. Not really a big deal since the PO number doesn't change, but I would like

to have this working perfectly.

The actual database is hosted on filemaker server 11 and we use both regular and advanced 11 clients.

Thanks,

Fred

Automatic message

This topic has been moved from "FileMaker Product Family → FileMaker Pro 11" to "Database Schema & Business Logic → Calculation Engine (Define Fields)".

Thanks Lee... New here and wasn't sure where to put it.