Record ID properties in FM5
bja...@montanaport.net
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.
Thanks much,
Bill
Helpful Harry
<6f40755a-8d07-4712...@p10g2000prf.googlegroups.com>,
"bja...@montanaport.net" <bja...@montanaport.net> wrote:
The RecordID is basically an internal field that FileMaker uses to keep
track of individual records, so an unique number is given to each
record when it is created.
Technically you can use this to identify records, but there is no
flexibility (eg. you cannot change this "field"). The RecordID is also
not static. If you import the records into another database (eg.
importing from a corrupt file into a fresh copy), then the record will
not necessarily get the same number.
It's usually much better to define your own "ID" field and use the
Auto-Enter Serial Number option.
Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)
Lynn Allen
<bja...@montanaport.net> said:
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
bja...@montanaport.net
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
Helpful Harry
<d895d30d-ba61-4031...@p31g2000prf.googlegroups.com>,
"bja...@montanaport.net" <bja...@montanaport.net> wrote:
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.