On Dec 7, 2007, at 3:07 PM, Brad Perkins wrote:
You will either have to have your Active4D code loop and wait until the record is unlocked and writable, or check for those conditions and and let the Active4D record know that record can't be saved. If you have 4D Client users that open records for a long time then the first solution is probably not ideal. The second solution takes some work on your part (See DISPLAY SELECTION vs MODIFY SELECTION).
Take a look at library routine a4d.utils.unlockAndLoad. It has a number of options that should take care of option 1.
Steve _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
