If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
When to base a form on a table?
Relating to my earlier post on suppressing record
scrolling on a form how do you decide whether to base a form on a table or not? If I have a form where a user will enter data that returns a specific record from a table should I base this form upon a table? Or just write some SQL to get the specific data and attach it to an event on the form? Thanks |
#2
|
|||
|
|||
When to base a form on a table?
I would limit the recordsource to the one record you want
to return. Otherwise, you have to populate unbound controls and handle all the updating. Too much work. You can open the form using the wherecondition clause: DoCmd.OpenForm "frmInput",,,"ProductID=1" Chris Nebinger -----Original Message----- Relating to my earlier post on suppressing record scrolling on a form how do you decide whether to base a form on a table or not? If I have a form where a user will enter data that returns a specific record from a table should I base this form upon a table? Or just write some SQL to get the specific data and attach it to an event on the form? Thanks . |
Thread Tools | |
Display Modes | |
|
|