If you are referring to the RecordID that FileMaker creates for each record, it is
accessible with the function Status(CurrentRecordID) in FileMaker or -recid in CDML. I
don't know what it is in AppleScript, but you can get it there, too.
As far as "using", it's unique enough if you're dealing within the database, but
shouldn't be used as a relationship key. It's NOT sequential (as we think).
Set up another field to auto-enter a serial number and pass that back.
Beverly
Hello, Nicholas Froome! On 10/10/2002 3:03 PM +0100, you wrote in
whole or part:
>As far as I know the internal database unique id is inaccessible
>from outside (or even inside) Filemaker, so don't bother trying to
>use it
>
>You can do serial numbers in variables, but I wouldn't recommend it.
>I'd use a Global field in FM to store the current serial number
>(generated from whatever scheme you like) and punch this into the
>serial number field when the record is inserted. You can then
>increment the Global field ready for the next insert
>
>A good reason not to use the internal unique id, as a key or for
>anything else, is that this value may change, I believe, under
>certain circumstances. These may include saving a compressed copy of
>the database
>
>I'd use your own generated unique ID as the key, always, with FM
>
>
>>I'm using witango on a Mac server linked to a filemaker database
>>which is used as a job booking system. What I would like to do is
>>provide a job ID number back to the person booking the job when
>>they add a new record, in the response page. The manual says that
>>witango can do this and will get the data back from the newly
>>created record, but goes on to say that the primary key columns
>>must appear in the Columns list of the builder. This is where I get
>>a bit stuck. I have included what I think is the correct field name
>>in the response html, but get nothing. I have tried to drag the
>>special record ID field into the Columns of the record building and
>>I get a message to say that it can't be put in the the list as it's
>>a special field.
>________________________________________________________________________
>TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
> with unsubscribe witango-talk in the message body
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
