Hi Sepehr, > Thanks for the reply. Ok I see what I wrote is a bit confusing. No the > intention is that there is a one to one relationship between the two tables.
(Hmm, in this case I wonder why you don't add the "Print" option to the "Main" table, instead of having it in a separate table, but that's another story.) > Main:MainID to PrintList:MainID. I want to have a form that lists all the > contents of Main and has a check box column for PrintList:Print. I want to > be able to scan through the entire Main table (in a particular order) and > select items that I will print by selecting them. Suggestions? Hmm. Master form bound to main, sub form bound to PrintList, connected via MainID/MainID (as master/detail fields of the sub form). In this simple form, this will probably be a somewhat clumsy UI, since the user would need to focus a sub form control (the "Print" checkbox), and pres the "new record" button before checking it. Surely not what s/he expects. If you don't like this (which I could understand :), add a "Print" check box to the main form, but when it's clicked, execute a macro which inserts/updates the PrintList table. You'd also need to intialize it every time the form moves to a new record. Other than that, I don't have an idea ATM. If you wouldn't need update but only display capabilities, you could base your form on a joined query ... But yes, that's not what you want. Sorry, no more ideas except the Basic macros. 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]
