ACCESS FEED: RE: [MS_AccessPros] General Table structure

Senin, 02 Maret 2015

RE: [MS_AccessPros] General Table structure

John and Crystal.

Thanks for the discussion. I see how it would be possible to do it in one table but I have decided to keep the tables separate. It is easier in my mind that way. Yes, I just put together a process for tracking purchase orders this weekend. It is working pretty well. I do have another question for either or both of you. I will start a new thread.

Thanks,

Bill

Ph: 763-754-8898

Toll Free: 877-902-8898

From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com]
Sent: Saturday, February 28, 2015 1:08 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: Re: [MS_AccessPros] General Table structure

Crystal-

If Bill is also keeping track of Orders and Purchase Orders in the database, it would be better to have separate tables because otherwise you would need to link Contacts to both tables - ugly.

John Viescas, Author

Microsoft Access 2010 Inside Out

Microsoft Access 2007 Inside Out

Microsoft Access 2003 Inside Out

Building Microsoft Access Applications

SQL Queries for Mere Mortals

http://www.viescas.com/

(Paris, France)

On Feb 28, 2015, at 4:27 AM, Crystal strive4peace2008@yahoo.com <mailto:strive4peace2008@yahoo.com> [MS_Access_Professionals] <MS_Access_Professionals@yahoogroups.com <mailto:MS_Access_Professionals@yahoogroups.com> > wrote:

Hi Bill,

To add another idea:

keep contacts together and then create a cross-reference table for the contact category (ie: Customer, Vendor) -- that way, the information needs only be entered once and is easier to keep up to date if a contact changes. This is what is done here in my Contact template:

http://msaccessgurus.com/Contacts.htm

Warm Regards,

Crystal

*

(: have an awesome day :)

*

On Saturday, February 21, 2015 1:36 AM, "John Viescas JohnV@msn.com <mailto:JohnV@msn.com> [MS_Access_Professionals]" <MS_Access_Professionals@yahoogroups.com <mailto:MS_Access_Professionals@yahoogroups.com> > wrote:

Bill-

Separate tables would be better.

John Viescas, Author

Microsoft Access 2010 Inside Out

Microsoft Access 2007 Inside Out

Microsoft Access 2003 Inside Out

Building Microsoft Access Applications

SQL Queries for Mere Mortals

http://www.viescas.com/

(Paris, France)

On Feb 20, 2015, at 11:37 PM, 'Bill Singer' Bill.Singer@at-group.net <mailto:Bill.Singer@at-group.net> [MS_Access_Professionals] <MS_Access_Professionals@yahoogroups.com <mailto:MS_Access_Professionals@yahoogroups.com> > wrote:

I am putting a database together to assist my son in his small business.

He have vendors that he buys from and he has customers that he sells to. In general the information in these tables are similar but not exactly the same.

Would it be best to put them in separate tables or the same table with a key field that distinguishes them from each other, such as 1 = Vendors, 2 = Customers.

I just thought I would ask before I get too far into this.

Thanks

Bill

Minnesota.

[Non-text portions of this message have been removed]