Re: Clients - internal and external, how design and process?
- From: "Gina Whipp" <NotInterested@xxxxxxxxxxxxx>
- Date: Mon, 27 Aug 2007 20:15:28 -0400
MSCeritfied,
Here's my two cents worth... Why not create a custom autonumbering field
that no one sees but you. IF you have a way to determine which ones are
external/internal, assign the external as odd numbers and the internal as
even numbers. This you have one table to create queries from and you have a
way to uniquely identify them.
--
Gina Whipp
"I feel I have been denied critical, need to know, information!" - Tremors
II
"mscertified" <rupert@xxxxxxxxxxxxx> wrote in message
news:97F87F14-FA94-4515-BE73-D7C591E957E4@xxxxxxxxxxxxxxxx
My application must cater for internal and external clients. Internal
clients
are employees who are maintained in an existing table which is updated by
importing from another database (which I have no control over). External
clients are people outside the company. The information to be kept will be
partly the same (name/address/phone no) but partly unique for internal or
external clients.
However, I will need treat these two types of client as a single entity
in
many queries and forms. What is the best way to set this up? I'm leaning
toward keeping the data in two separate tables but having a query that
draws
both together. However, this query will not have any common column to
uniquely identify the client and I can see that being a problem.
.
- Follow-Ups:
- Re: Clients - internal and external, how design and process?
- From: Pat Hartman \(MVP\)
- Re: Clients - internal and external, how design and process?
- Prev by Date: Re: need access to read to SQL db and Access frontend
- Next by Date: Re: need access to read to SQL db and Access frontend
- Previous by thread: Re: need access to read to SQL db and Access frontend
- Next by thread: Re: Clients - internal and external, how design and process?
- Index(es):
Relevant Pages
|
