<i><font color="#663300">This is where sequence is required not UniqueIDs.
Could we have a CBNewID() with an extra parameter that just returns the current value assignable not necessary given. Just a simple lookup and return the value on a call like CBNewID(.F., .T.) or CBNewID("PONO", .T.). The second para say just lookup and thats all.
When the BO does the actual save only then the real CBNewID() is assigned, we could have checks for the retunred value being the same as the originally retuned if so warn the user and override with the new value.</font></i>
Instead of that, why not just assign a value of "-New-" when the order is created, and then give it an actual value upon Save()? In my experience, users will understand that the number is not assigned until the order is saved.
<font color="#cc0000"> ___/
/
__/
/
____/</font>
Ed Leafe
©2001 Ed Leafe |
