Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Database Design / April 2005

Tip: Looking for answers? Try searching our database.

Problems with Relationship

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
rasper22 - 14 Apr 2005 04:29 GMT
Hi

I am designing a call logging system for my business. That records all
the details of calls received and then displays all the records that
have not been resolved.

Suppliers can have more than one account with us. And are able to
query more than one invoice from different accounts in on Call.

Business Scenario:

A supplier makes a call and we enter the persons name and contact
details. We then record all the invoices and the account it relates
to. We then rank the status of each query as Active, Pending or
Resolved.

This is really basic I know but I keep getting stuck.

At the moment I have three tables: Suppliers, Call, Querry Details
Suppliers 1:M Calls and Calls 1:M Querry Details?

Using this option I am not able to select a different Acc for the
supplier under the Calls table?

Regards,

Franz  :roll:

Signature

Posted using the http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbforumz.com/Tables-DB-Design-Problems-Relationship-ftopict214362.html
Visit Topic URL to contact author (reg. req'd).  Report abuse: http://www.dbforumz.com/eform.php?p=733867

BruceM - 14 Apr 2005 12:30 GMT
"And are able to query more than one invoice from different accounts in on
Call."
Even assuming you mean "one Call" I can't quite sort out what you need to
do, but it seems to me you need an accounts table.  Do you mean to say that
in one call the supplier can find out about multiple accounts?  If each
supplier can have multiple accounts, and each account can have multiple calls
associated with it, then you need an accounts table.  I don't understand what
a "query detail" is, but if each {Whatever} can have multiple associated
queries, {Whatever} is on the one side of one-to-many.

> Hi
>
[quoted text clipped - 23 lines]
>
> Franz  :roll:
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.