Re: [MS_AccessPros] Forms Work Practices

 

David-

I tend to have a common form design for all tables, with subforms or tabs used as appropriate to edit related data.  I will also sometimes design an "add one row" form to be invoked from the Not In List event of combo boxes.

For example, I might have a form called frmCompany to edit company data and a form called frmCompanyAdd that gets opened as a dialog from, perhaps, the company combo box on a form to edit contacts.  See the sample database I suggested you download in my previous message.

John Viescas, Author

Effective SQL

SQL Queries for Mere Mortals 

Microsoft Access 2010 Inside Out

Microsoft Access 2007 Inside Out

Microsoft Access 2003 Inside Out

Building Microsoft Access Applications 

http://www.viescas.com/ 

(Paris, France)

On Feb 28, 2017, at 6:14 PM, david.pratt@outlook.com [MS_Access_Professionals] <MS_Access_Professionals@yahoogroups.com> wrote:

Looking for experienced developer advice...

For your typical design work, do you typically have certain types of forms for each table?  i.e. do you typically have a form that is used for adding records, one for viewing records, one for editing records, etc.  Or do you typically have a single form that is used for multiple actions?

I know there is not a one size fits all, but on a typical basis?

__._,_.___

---

Posted by: John Viescas <johnv@msn.com>

---

Reply via web post

•

Reply to sender

•

Reply to group

•

Start a New Topic

•

Messages in this topic (2)

---

Have you tried the highest rated email app?

With 4.5 stars in iTunes, the Yahoo Mail app is the highest rated email app on the market. What are you waiting for? Now you can access all your inboxes (Gmail, Outlook, AOL and more) in one place. Never delete an email again with 1000GB of free cloud storage.

---

Visit Your Group

• Privacy • Unsubscribe • Terms of Use

.

__,_._,___