Bestway to set up a database for the following:

[Guest]

I am setting up a database that will track our production schedule and also
be useful for history etc. Need some feed back that I am setting up the
correct way. I understand there is a need to FE forms and queries and BE for
the data table. Question is this: I have generated a form that basically
fills 2/3 of the fields for a data record. The rest of the fields need to be
entered as information becomes available and status changes. What is the
best way to update these fields in a record. We will be having 5-8 people
updating at various times. Thank you in advance for any help you can offer.

 

[Guest]

You did not give enough information. What kind of data will you collect?
What will the data be used for? What kind od report and analysis? Is it
production per employee or per day, shift, hour? Raw materials quanity,
cost, waste, rejects, labor, setup, maintenance, etc.

 

[John Vinson]

I am setting up a database that will track our production schedule and also
be useful for history etc. Need some feed back that I am setting up the
correct way. I understand there is a need to FE forms and queries and BE for
the data table. Question is this: I have generated a form that basically
fills 2/3 of the fields for a data record. The rest of the fields need to be
entered as information becomes available and status changes. What is the
best way to update these fields in a record. We will be having 5-8 people
updating at various times. Thank you in advance for any help you can offer.

If you can enter the data into new records in a Form, you can use
exactly the same form to edit fields in existing records. You may want
to add a combo box (the wizard will provide this as one of the
options) to locate the record to be edited, but other than that the
exact same form will work just fine.

John W. Vinson[MVP]

 

[Guest]

Karl,

Thanks for the interest. We will be tracking the following:
Salesman
Amount
Customer
Ship to
Hauler
Model
S/n
date equipment will be ready
(epuipment ready yes/no)
date site will be ready
(yes / no)
who the installer is
has equipment been installed (yes/no)
invoice date
invoice yes/no

Dates can change and do often. Almost 2/3 of this info can be entered when
the data is first entered. The rest is entered as information becomes
available. (This needs to be as "user friendly" as possible).

Again, any help would greatly be appreciated. Thanks in advance,

Nick

 

[Guest]

This table structure should do what you want.

Salesman ---
SalerID – Autonumber – primary key
LName – text
FName – text
MI – text
PrefName – text
HireDate – DateTime
Position - text

Customer ---
CustID – Autonumber – primary key
Company – text
Phone – text
Ext - text
Fax - text
Address1 – text
Address2 – text
City – text
State – text
ZIP - text
BillAddr1 – text
BillAddr2 – text
BillCity – text
BillState – text
BillZIP - text
ShipAddr1 – text
ShipAddr2 – text
ShipCity – text
ShipState – text
ShipZIP - text

Sale ---
SaleID – Autonumber – primary key
SalerID – number – integer – foreign key
CustID – number – integer – foreign key
SiteDate – DateTime (date equipment will be ready)
SiteReady – Yes/No
EquipDate – DateTime (date site will be ready)
EquipReady – Yes/No
InvoiceDate - DateTime
Invoice – Yes/No
Amount – number - integer

Ship ---
ShipID – Autonumber – primary key
SaleID – number – integer – foreign key
ItemNo - text
ShipTo – text (Ship To address, company address, bill address, other)
Hauler – text
Model - text
SerialNo - text
Installer - text
Installed – Yes/No

Set up one-to-many relationship from the primary key fields to the foreign
key fields. Use a form/subform to display the one-to-many relationship.