Jump to content

This topic is 4647 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies
Posted

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

This topic is 4647 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.