Use the -same- form and hide the controls you don't want to use if the mode is "simplified".
-- -Richard M. Hartman [EMAIL PROTECTED] 186,000 mi/sec: not just a good idea, it's the LAW! Borislav Kolev wrote in message <[EMAIL PROTECTED]>... > >Hi! > >A form in one of my applications has a dual appearance - complete and >simplified. Obviously, the simplified is only a subset of the complete and I >though I can easily arrange the implementation by making a copy of the >full-blown form resource, rearrange it and mark most of the elements that I >don't need hidden or even delete it. Then, with a small change in the >complete form code I expected to have it handle both cases. > >Alas, Constructor stops me from doing so: it insists on having unique IDs >for all controls in all resources! Is there an OS-driven reason for that? To >the best of my knowledge there shouldn't be, because the list with form >objects is strictly linked to the form structure itself and therefore could >not interfere with other forms. > >Any suggestion for "smart" workaround? I could replace all references to >object IDs in the code with variables that I would initialize first, but I >don't like that. I could also modify the code of the full-blown form to >dynamically rearrange itself, but don't like this either - actually, it >already does something similar and another layer on top of it would make >complete mess. > >Help! > >Thanks, >Bobby > > -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
