It also has restrictions as in there is a slight possibility of there being two numbers that are the same - but you can code for that problem/catch the error and respond accordingly.
You need a table which will hold the ID (number that increments or string or whatever). Your code grabs the number, increments it and returns it to the table, holding the original number back for your process (use a function).
This in theory over a multi-user network with fastish connections should work without conflict, but you'd know if you have a conflict when you save the record. Please note this is more for Unbound forms than the crap bound forms and that if you create a number it is always incremented, otherwise the chances of clashing unique numbers is increased.
Or, if its just a display problem (like you need QUREF000100 for record 100), I'd use a format command or format on the text box and keep the unique ID. You can always keep the autoincrement as the record ID but use another field for the displaying ID...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.