Re: Stuck, Oredering form, Any ideas?
- From: "tina" <nospam@xxxxxxxxxxx>
- Date: Sun, 14 Sep 2008 16:55:30 GMT
yes. don't try basing an Orders data entry form on a multi-table query. you
don't need it, and there's a good change it wouldn't be updateable after
you'd written it. having said that much, let's forget about forms for a
minute and concentrate first on building a table to store the orders. i'm
guessing that you may need to order multiple uniforms at one time, but want
to tie each uniform to a specific employee. i'll also assume that each order
goes to a single supplier; in other words, if you're ordering x article from
supplier A and x articles from supplier B, you'll enter a separate order for
each supplier. if that's correct, you need two tables, as
tblOrders
OrderID (primary key)
InvoiceNumber (if you need it. and if it's unique, you may use that as the
primary key instead of having the OrderID field - but, in any case, DON'T
use autonumber to generate an invoice number because there *will* be gaps in
the sequence sooner or later, and probably sooner.)
OrderDate
Supplier (foreign key from tblSuppliers)
<other fields that describe the order *as a whole*, but don't describe order
details, or supplier details - unless that supplier detail is *specific to
the order*, NOT merely specific to the supplier. also, do NOT include a
field for the total cost of the order, that should be a calculated value;
though you may include a field for a discount amount or percent, a tax rate,
a shipping charge - hard values that apply to the specific order *as a
whole*.>
tblOrderDetails
DetailID (primary key)
OrderID (foreign key. if you use an invoice number as primary key for
tblOrders, then use it as the foreign key in this table, instead of
OrderID.)
Article (foreign key from tblArticles)
Size
Color
Price
EmployeeID (foreign key from tblEmployees)
using the above table setup (which is an *example*, remember), your forms
setup would be: a mainform bound to tblOrders. the Supplier field would be
bound to a combobox control in the mainform, with the combobox's RowSource
set to tblSuppliers, so you can choose a supplier for the order. a subform
bound to tblOrderDetails, with the LinkChildFields property set to OrderID
(the foreign key field in tblOrderDetails), and the LinkMasterFields
proeprty set to OrderID (the primary key field in tblOrders). the EmployeeID
field would be bound to a combobox control in the subform, with the
combobox's RowSource set to tblEmployees, so you can choose an employee for
the order.
hth
"Dale G" <DaleG@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:66455C55-A665-4A46-AC86-D16691BD5174@xxxxxxxxxxxxxxxx
I'm trying to create a data base for ordering employee uniforms at myplace
of employment.that
So far I've created the following tables, Employee, department, Gender,
Article, supplier.
I'm stuck on how to set up a table for uniform orders, and then combine
with my Employees table, in a Query. From there I would like to create anphone,
order form using that query. Any ideas?
My employees table has the following fields, ID autonumber, Employee id,
Last name, first name, anniversary date, Job title, home phone, cell
address, city, state, zip code, e-mail.
I also have a query Employee Extended, this is Similar to the example
(Northwind).
I can't find any examples to follow. If possible I would like part of the
form, the employee part, to Auto fill.
I'm thinking the form should have employee Info, info about the article
ordered, date ordered, date received, duration between ordered & received,
cost, & integrity of received Order.
Any suggestion will be appreciated.
.
- References:
- Stuck, Oredering form, Any ideas?
- From: Dale G
- Stuck, Oredering form, Any ideas?
- Prev by Date: Stuck, Oredering form, Any ideas?
- Next by Date: Re: Stuck, Oredering form, Any ideas?
- Previous by thread: Stuck, Oredering form, Any ideas?
- Next by thread: Re: Stuck, Oredering form, Any ideas?
- Index(es):
Relevant Pages
|
