Re: Help with relationships

This is to be a Requisition Request. As for the vendor I would like to have a
combobox that when I select the vendor, all the other information about the
vendor will populate the other fields in the vendor table. The request table
is all the other infomation like the unit (area that orders) requester
(person requesting) others like OBcode and Account will come from a
predetermined list of accounts and object codes. The last table cost will
never be predetermined. There are to many types of services (consulting) that
will change from requisition to requisition. When the report is printed, it
will create a form that we would send to our finance and support area for
processing. Hope this helps. I will read the artical you suggested and try
to get things straight. Thank you.

"tina" wrote:

> how are requests related to vendors *in the "real" world*? and how is cost
> related to either entity, or both - again, in the "real" world? also, what
> is the primary key of each table, at this moment? we need to understand the
> process you're tracking with this database, before we can make suggestions
> for a normalized tables/relationships design.
>
> also, suggest you read up on data modeling. in the final analysis, *you* are
> the best person to design your tables/relationships because you know (or
> should know) more about the process and the entities involved than you can
> hope to tell us in a newsgroup forum. for more information on data modeling
> and normalization, see http://home.att.net/~california.db/tips.html#aTip1.
>
> hth
>
>
> "Mike Busch" <wizof103@xxxxxxxxxxx> wrote in message
> news:2ED43AE1-2D79-458A-BFFA-870D11733A5B@xxxxxxxxxxxxxxxx
> > Need help with relationships. This is for a form that hopes to produce a
> > report for work.
> > The Tables are as follows:
> > tblRequest
> > MISNumber - Number
> > Requester - Text
> > Unit - text (this is an area)
> > Account - Text
> > OBCode - Text
> > Description - Text
> > Justification - Text
> > Category - Text
> >
> > tblVendor
> > MISNumber - Number
> > Vendor - Text
> > Address - Text
> > State - Text
> > Zip - Text
> > PhoneNumber - Number
> > Contact - Text
> > FedId - Text
> > ContactNumber - Number
> >
> > tblCost
> > Quanity - Number
> > UnitofMeasure - Text
> > UnitPrice - Currency
> > TotalCost - Currency
> >
> > The tblRequester and tblVendor are easy with the MISNumber, any
> suggestions
> > for the tlbCost table. Thanks in advance
> >
>
>
>
.

Relevant Pages

  • [Full-disclosure] URL filter bypass in Fortinet
    ... URL filter bypass in Fortinet ... Affected products: FortiGate v2.8 ... - if each line of the request is terminated by CR instead of CRLF ... 08/16/2005 The vendor asked for more information ...
    (Full-Disclosure)
  • URL filter bypass in Fortinet
    ... URL filter bypass in Fortinet ... Affected products: FortiGate v2.8 ... - if each line of the request is terminated by CR instead of CRLF ... 08/16/2005 The vendor asked for more information ...
    (Bugtraq)
  • KPMG-2002004: Lotus Domino Webserver DOS-device Denial of Service
    ... The Domino Webserver does not handle URL request for DoS-Devices ... the server will no longer accept requests. ... Vendor URL: ...
    (Bugtraq)
  • KPMG-2002013: Coldfusion Path Disclosure
    ... Requests for non-existant .cfm and .dbm files return a coldfusion ... "Error Occurred While Processing Request ... Error Diagnostic Information ... Vendor URL: ...
    (Bugtraq)
  • Re: Help with relationships
    ... presumably each requisition will be filled by one vendor. ... VendorID field in tblRequisitions as a foreign key. ... >> VendorID (primary key, probably Autonumber data type) ...
    (microsoft.public.access.gettingstarted)