Simple Database for Dealership

[CALAN]

We have a truck dealership and I am using FM to keep track of inventory and customers. Now I want to create invoices out of FM. Since each inventory item only has one sale (one invoice) and one customer, do I need a separate table for invoices? One customer might buy several trucks, but each would be invoiced separately. Would the invoice just be an attribute of inventory? I am having such trouble getting this to work right. Can anyone help me get this started right. Everything I try doesn't seem to work right.

Thanks alot

Cathy

[Fitch]

One table for customers, and one for inventory might be OK. But don't you sell other things like parts and service? Seems like in those cases you might have multiple items per invoice.

[jrr316]

I would use A Separate Table for Invoices, that i just good design.

I have built system like this before if you wuld like some assistance

-Justin

http://reddenconsulting.com

[CALAN]

No, we won't use this database for anything but truck sales. I use quickbooks for misc sales. If I create a separate table for invoices, it will be a one to one join? By stock #? Then invoices is joined to customers? Difficult for a beginner LOL

[CALAN]

I would love help. I have looked for someone for counsel, but haven't found anyone. I have been using the inventory table for over a year now, and it works great to track inventory and I linked it to customers, but having trouble with the invoices and payments.

Cathy

[comment]

The only reason I can see for having a separate table for invoices is to make sure they are numbered sequentially.

And yes, it would be a one-to-one relationship, using the unique ID field in your inventory table as the common value.

Edited October 3, 2008 by Guest

[Fitch]

You would probably want a separate table for payments, linked to the invoice by invoice number.