Re: Is there a better way > Auto Enter Serial Number in FMPro 9?



On Sep 30, 12:00 pm, Grip <g...@xxxxxxxxxxxxx> wrote:
On Sep 29, 11:45 pm, d-42 <db.pors...@xxxxxxxxx> wrote:



On Sep 29, 11:26 am, EJay Corvette <Eric.J.Merch...@xxxxxxxxx> wrote:

I've been searching for a couple days now for the solution to
resetting the "Record Number" in my database. The Record Number is a
Serial Number and should increment by 1.

The problem I'm having is whenever a record is deleted (usually the
last record entered), my numbering is off, and I have to manually
reset the Serial Number before someone inadvertantly starts a new
record.

For example, if my records are 09, 10, 11, 12, and record 12 is
deleted, the Serial Number will then install 13 as the next available
record number.

I was able to locate this simple looking enough script from the web:

Enter Browse Mode []
Allow User Abort [Off]
Show All Records
Unsort Records
Go to Record/Request/Page [Last]
Set Next Serial Value [Client Records::Record No + 1]

The problem is, I can't get it to work. Anybody out there have a
solution?

Well, the allow user abort is superfluous. The rest of the script
looks fine; except that it appears that you haven't specified which
field to set next serial value. You've told it what to set it *to*,
but not what to set.

The bigger question is -why- are you doing this? The need to reset
serial numbers, except after an import, is usually a design error.
There are cases where its justified. But for the most part, we only
require that serial numbers be unique, not sequential with no gaps in
the numbers.

An exception, for example, might be invoice numbers, where you don't
want gaps, but in that case its usually better not to be able to
delete records at all, period. If a record is created that you don't
want, mark it as void. Or alternatively, don't assign it an invoice
number until you are sure you want to keep it. (Assign it an order
number or reference number until your sure its a keeper.)

-cheers,
Dave

What are the circumstances in which you use Allow User Abort?

Most of the time Allow User Abort should be off. You don't normally
want users to abort your script in mid-execution.

Typically you'd only want to allow abort if the script is going to
take a long time to run, and you want to give users an out, or during
design/testing/debugging, when you don't want to to have to wait for a
script to finish, or worse, get yourself into an infinite loop.

I said the step was superfluous because it wasn't relevant to the
issue at hand.

-dave

.



Relevant Pages

  • Re: Is there a better way > Auto Enter Serial Number in FMPro 9?
    ... I was able to locate this simple looking enough script from the web: ... the allow user abort is superfluous. ... An exception, for example, might be invoice numbers, where you don't ... want gaps, but in that case its usually better not to be able to ...
    (comp.databases.filemaker)
  • Re: Preview mode with pause, capture user abort
    ... > Enter Preview Mode [Pause] ... > Go To Layout ... I couldn't get to work that script properly, ... > the Allow User Abort option is better since that stops users being able ...
    (comp.databases.filemaker)
  • Re: link between logins and cards
    ... As long as you script the user access, you may put some control lines in the ... 'Allow user abort ' // at the beginning of the script ... 'Go To Layout (Nominative) ...
    (comp.databases.filemaker)
  • Re: Preview mode with pause, capture user abort
    ... I'm not sure about capturing the abort in the script, ... User Abort Off. ... Enter Preview Mode (Pause) ...
    (comp.databases.filemaker)
  • Re: Is there a better way > Auto Enter Serial Number in FMPro 9?
    ... the allow user abort is superfluous. ... The need to reset ... An exception, for example, might be invoice numbers, where you don't ... want gaps, but in that case its usually better not to be able to ...
    (comp.databases.filemaker)