Record ID properties in FM5

On 2008-10-27 07:18:02 -0700, "bjaynes@montanaport.net"
said:

> The Status(Current Record ID) function appears to return an
> incrementally larger number each time a record is started.Is that 100%
> reliable, that is, that is always a larger number? I could really use
> this in a sorting problem.
> PS Haven't been here for a while. Immediately cheering to see Harry
> and Lynn here.

Well, I was gone, then I came back.

Yes, Record IDs are always larger in creation order. I haven't tested
whether they sort by number or as text, which are different.

As Harry points out, Record IDs are not persistent. If you base a
creation sort on them, then sort by another field and import into a
clone, your creation sort is screwed.

Try this: Append a serial and a creation timestamp into a number
string, Timestamp first. Then sort by that field. It will persist
through all imports and be unique.

In fact, that's what I use for my keys. I don't need to reset the
serials after import, and the timestamps always ensure that even
repeated serials don't create a duplicate key.
--
Lynn Allen
--
www.semiotics.com
Member Filemaker Business Alliance
Long Beach, CA
 >> Stay informed about: Record ID properties in FM5 

Thanks Harry,
I use the Auto Enter Serial option in other situations
but in this case, a more robust number field would
be useful.
If I have a number field Auto-Enter Status(Current RecordID),
wouldn't it, thereafter, be just a static number field?
Bill
 >> Stay informed about: Record ID properties in FM5 

In article
,
"bjaynes@montanaport.net" wrote:

> Thanks Harry,
> I use the Auto Enter Serial option in other situations
> but in this case, a more robust number field would
> be useful.
> If I have a number field Auto-Enter Status(Current RecordID),
> wouldn't it, thereafter, be just a static number field?
> Bill

That would work, as long as when importing into another database you
remember to turn OFF the perform Auto-enter options. Other than not
being able to reset the counter, I can't really see why this would be
"more robust" than a normal Serial Number Field though.

Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)
 >> Stay informed about: Record ID properties in FM5