Hi Larry, As well as the afore mentioned, all excellent comments, you can use the 'if exists(fld "myField01") then' script. I also encapsulate all sorts of things in "try"..."end try" commands. These are extremely powerful although could be considered a little lazy. For example, when using iPhone commands I sometimes lazily put them inside "try"s in an effort to prevent them causing a problem when testing on the desktop. So, "try ¬ delete field myField01 ¬ end try" does not cause a lasting problem. Using a Catch pError inside the try will help out if you need to detect if it has been deleted/exists or not.
All the best Sean Cole *Pi Digital Productions Ltd* www.pidigital.co.uk On 13 October 2014 18:53, Geoff Canyon <gcan...@gmail.com> wrote: > One caveat: if you are assembling a great deal of text in small chunks, > you should likely do it in a variable and then toss it into the field in > one go. Field updates are slower than many (most?) other things you might > be doing, and one field update with 10,000 lines will be *much* faster than > 10,000 updates with one line each. > > gc > > > On Oct 12, 2014, at 10:58 PM, J. Landman Gay <jac...@hyperactivesw.com> > wrote: > > > > The display and update of the dialog is likely to take longer than just > creating the fields. > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
