Forum Discussion
QuickBaseCoachD
Qrew Captain
Deb,
Another solution is to simply use the [Record ID#] to make a formula field to make a sequential number based off the Record ID# field.
ie "C-" & ToText([Record ID#])
It will not start with the Year number. You can import from excel and delete enough records to roll the record ID# ahead to say 30,000 and just count forward from there.
You may want to number based on the year, but there may really not be a good reason to do that, other than that is always how you used to do it.
So, I'm just offering up an alternative solution.
Another solution is to simply use the [Record ID#] to make a formula field to make a sequential number based off the Record ID# field.
ie "C-" & ToText([Record ID#])
It will not start with the Year number. You can import from excel and delete enough records to roll the record ID# ahead to say 30,000 and just count forward from there.
You may want to number based on the year, but there may really not be a good reason to do that, other than that is always how you used to do it.
So, I'm just offering up an alternative solution.
QuickBaseCoachD
6 years agoQrew Captain
Y es, but in these situations I always feel better if the [Record ID#] is the Order number or claim number, whatever the table represents. I just think it�s worth taking the five or 10 minutes to load up an Excel sheet import a bunch a records and delete them. It is like once in your life that you spend is 10 minutes and then for the eternity there�s no confusion over the difference between those two numbers. For example maybe the user is doing a search on order number 12345. This way they will only get one yet unless that number happened to appear in some other field.