Re: Line Item Issue
- From: "Mike" <thewittmer@xxxxxxxxx>
- Date: Tue, 03 May 2005 13:07:25 GMT
Thanks John. I'm looking into your suggestions. The table does link
records together by a ticketnum key.
"John Nurick" <j.mapSoN.nurick@xxxxxxxxxxxxxx> wrote in message
> Hi Mike,
> You need to think hard about the semantics of the situation. In
> relational database terms, a table that contains three different kinds
> of record which have no fields in common is not a table at all, it's
> unworkable nonsense.
> In any case, you already have the data in the three tables, so you don't
> need to duplicate it in a fourth table. Instead, use queries to
> assemble/combine the data you need as and when you need it - although
> unless the existing tables are related on some field you haven't told us
> about, I'm not sure that that will be possible.
> On Tue, 03 May 2005 03:04:11 GMT, "Mike" <thewittmer@xxxxxxxxx> wrote:
>>I have a LineItem table that needs to pull data from one of 3 tables;
>>sinventory, nsinventory, serviceitem - depending on the state of an
>>field within the LineItem table. The structure required for each item
>>type varies for any given option. nsinventory has a product field and a
>>field, sinventory has a product field and a serailnum field, serviceitem
>>a servicetype field and a memo field. I'm stuggling with what is the best
>>approach to handling this. Currently my 'best' idea is to create a table
>>that contains all 6 fields of which only 2 will be of significance for
>>record. This seems a bit cheesy and creates an issue when displaying data
>>that will need to be resolved programmatically.... I'm wondering if there
>>a better way.
>>Any suggestings would be appreciated.
> John Nurick [Microsoft Access MVP]
> Please respond in the newgroup and not by email.
- Prev by Date: Re: Line Item Issue
- Next by Date: Re: Line Item Issue
- Previous by thread: Re: Line Item Issue
- Next by thread: Re: Line Item Issue