<< C'mon Dennis/Larry.. Who would put a database maintenance activity in the midst of a data entry scenario? That's a non-starter. >>
Why use a potentially dangerous programming technique when the language offers a perfectly safe and equally easy alternative? If you leave a data-bound form around whose to say what another programmer might do to it in the future? Indeed, if it doesn't need to access the data in the table to which it's bound, why is it even a bound form in the first place? And, since the nature of data-binding is internal to R:Base (ie, we don't know how it works and it could change), whose to say whether a future optimization to the way bound forms work won't break existing forms that use this technique? I think that the best that can be said about this practice is that it "is unlikely to cause data corruption in the current version of R:Base and this application". I'd much rather be able to say to the client that the menu I wrote for them is guaranteed not to harm the database. -- Larry
