Forum Discussion
_anomDiebolt_
9 years agoQrew Elite
Here is a demo application that demonstrates a variety of ways you can requence the child records using Arabic, Roman or Revision numbering by pressing the appropriate button:
ReSequence Children
https://haversineconsulting.quickbase.com/db/bmnukbw5c?a=td
Pick a record to view and select one of the buttons to resequence the child records.
Pastie Database
https://haversineconsulting.quickbase.com/db/bgcwm2m4g?a=dr&rid=566
Notes
(1) The script uses two helper functions romanize() and toBase26() to define the sequencing scheme used but any function that converts an integer to some sequential symbol could be used. How about using Cuneiform numbers (https://en.wikipedia.org/wiki/Cuneiform_script) or tally marks (https://en.wikipedia.org/wiki/Tally_marks)?
(2) No formulas are used to do the sequential counting so the results will persists even if other fields change values or if child records are deleted. The buttons to sequence the child records should be performed administratively only when the child records needs to be sequenced (this might be a one time affair) and there is no need to maintain a historic record of prior sequencing.
(3) In all cases the child records ion my demo are naturally ordered in alphabetic order by [Name]. Whatever ordering of your child records is (by date, number, alpha etc) you should consistently use your sequencing convention so that the sequencing assigned by script stays consistent.
If you need assistance implementing this solution fee free to contact me off world using the information in my profile:
https://getsatisfaction.com/people/dandiebolt
ReSequence Children
https://haversineconsulting.quickbase.com/db/bmnukbw5c?a=td
Pick a record to view and select one of the buttons to resequence the child records.
Pastie Database
https://haversineconsulting.quickbase.com/db/bgcwm2m4g?a=dr&rid=566
Notes
(1) The script uses two helper functions romanize() and toBase26() to define the sequencing scheme used but any function that converts an integer to some sequential symbol could be used. How about using Cuneiform numbers (https://en.wikipedia.org/wiki/Cuneiform_script) or tally marks (https://en.wikipedia.org/wiki/Tally_marks)?
(2) No formulas are used to do the sequential counting so the results will persists even if other fields change values or if child records are deleted. The buttons to sequence the child records should be performed administratively only when the child records needs to be sequenced (this might be a one time affair) and there is no need to maintain a historic record of prior sequencing.
(3) In all cases the child records ion my demo are naturally ordered in alphabetic order by [Name]. Whatever ordering of your child records is (by date, number, alpha etc) you should consistently use your sequencing convention so that the sequencing assigned by script stays consistent.
If you need assistance implementing this solution fee free to contact me off world using the information in my profile:
https://getsatisfaction.com/people/dandiebolt