Hi Ariel, > This would be a great idea!!! (though what about backwards > compatibility? will it be too much code to implement - not to destroy > the users old data?)
meditated a little about this the last few days. The more I think about it, the more I like it. We could, for compatibility, leave everything as-is with old documents. That is, opening them would yield a warning "This document contains forms and/or reports with embedded macros. This is not recommended anymore. Please migrate the macros to the database document itself. Bla Bla Bla." Something like this, with more sugar added, of course. (One could even think about a automatic migration, though this would inevitably lead to conflicts in case we have equal-named functions/modules/libraries in different sub documents.) > The thoughts here are just what a "common"/"dummy" user would/could do > (let me tell you I've seen almost everything - mostly coming from former > MSAccess users without programming knowledge, and used to VBasic's Me , > DoCmd, etc.) > > Nevertheless the event binding problem in Forms will come to: if I go to > the dialog Tools-Customize-Events from a form-document, in the "Save in" > list box I should see the form-doc.'s parent == the DatabaseDocument Sure. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
