How would I make a field find the last sequentially numbered record and then add 100 to it?
If you have a summary field that computes the maximum of that field, sMax + 100 as an auto-entered calculation could do that, but care must be taken--especially for multi-user environments or you can get two records with the same number.
A better option would be to use an auto-entered serial number with an increment of 100 instead of 1.
The auto-entered serial number with an increment of 100 is what I'm trying to do. The problem is, the "100" is not being added to the largest number in the already existing records.
I want the new record to reference the largest number in the existing records and add 100 to it (So, if the last record is numbered 005100, the new number becomes 005200.)
It appears you are putting a number in a text field. (Otherwise, you won't get the leading zeroes shown.)
This works just fine if you use a number field. You can still display the leading zeroes with a calculation that looks like this:
Right ( "000000" & SerialNumberField ; 6 )
Then your increment by 100 should work and you still have your leading zeroes.
Actually, Phil, they are number fields. I entered the numbers originally using "Replace Field Contents" and they kept the leading zeros. I tried adding your calcuation; still not working. Any other ideas?
It does work. How exactly doesn't it work for you? That's an important clue not shared in your posts.
See this screen shot...
Right now, my records are numbered like 005100, 005200, 005300 and so on. I want a new record to be 005400.
Here are the screen shots. What am I doing wrong?
These are not auto-entered serial number settings. All I needed to do to produce the screen shot shown is to define the field as an auto-entered serial number, specify 00100 as the next value and 100 as the increment.
In your case, select 005400 as the "next value" and 100 as the "increment". There's no need for the calculation you have here.
OK, that's working, Phil. I was confused about how FileMaker would handle additional requests AFTER the "next value", but it's working the way I want it to.
Retrieving data ...