Relationships in Menu

[Con]

I am a Newbie and have a question that I just can't understand. I am designing a datebase that has Customers and invoices. On the Menu, I would like to have invoice and customer portal queries that I can open from there. What would be the relationships between menu, customer , & invoices.

Thanks

[T-Square]

Unless there's some business need, you are not required to have a relationship between tables. So, you could simply create buttons that open up your Customer and Invoice layouts in new windows.

Now, let me explain what I mean by "business need." Many applications don't just take a user to the next window in the chain, they perform all sorts of behind-the-scenes steps, like logging a user in, validating their access information, or limiting their view to a subset of records. All these steps are dictated by the needs of the business.

If you have any such need (or think you might down the road), you will need to find a way to accomplish these tricks. A lot of times, that entails setting some value in one central place (your Config table, say), and then managing the interface based on these settings. In that circumstance, you might find that using relationships between the Config table occurrence and your other table occurrences will quickly, easily, and securely render your business rules.

HTH,

David

[Con]

At this time I think that I will be the only one using the database. The reason for wanting to put the invoices and customers on a Main Menu with a portal is so, as an example, if I forgot what the name was I could scroll down until I found his name (Bill Johnson)and click on him and go to his customer layout. The Main Menu would work more as a command center.

[T-Square]

You could create a simple list layout (based on the Customers table) that shows basic customer info on a single line, with each line set as a button to display the selected record in another fuller layout.