Re: Clients - internal and external, how design and process?

I made and assumption (I know, I know) that one would know who was internal,
external based on this statement, "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)."

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

"BruceM" <bamoob@xxxxxxxxxxxxxxxx> wrote in message
news:eHXl$3j6HHA.5160@xxxxxxxxxxxxxxxxxxxxxxx
Whether an odd/even number or a letter, how would you assign it? That is,
how would Access "know" if the client is internal or external?

"Gina Whipp" <NotInterested@xxxxxxxxxxxxx> wrote in message
news:e29wETX6HHA.1148@xxxxxxxxxxxxxxxxxxxxxxx
Pat,

Perhaps I didn't expalin that clearly enough... I was not referring to
embedding the information but creating a seprate field/cloumn, mine would
just be odd/even numbers being created without the users knowledge. (I
always use custom automubering because the end-user has no use for the
number. Only I need it for design purposes.) However, you make a good
point about not limiting the choice to 2, so perhaps letters or some
other type of identifier is more appropiate.

Thanks for the feed back!
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors II

"Pat Hartman (MVP)" <please no email@xxxxxxx> wrote in message
news:uQYwtHX6HHA.3940@xxxxxxxxxxxxxxxxxxxxxxx
Gina,
Using even/odd numbers is a creative solution but inappropriate.
Embedding "hidden" information in a field is not good design practice as
well as being a violation of first normal form (all fields should be
atomic). A better solution is to create a new column that can be used
to distinguish the two different types of people. The new column is not
limited to two choices, should a third type of person be identified as
the design progresses.
Pat

"Gina Whipp" <NotInterested@xxxxxxxxxxxxx> wrote in message
news:%23X3CNiQ6HHA.5212@xxxxxxxxxxxxxxxxxxxxxxx
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.










.

Relevant Pages

  • RE: linking data from one table to another
    ... The Clients, Employees and Projects tables (or whatever you choose to call ... The WorkAllocations table, which models the relationship type between the ... shows your logical model is set up correctly. ...
    (microsoft.public.access.gettingstarted)
  • Design Issue (Employee and Client)
    ... I am trying to design a login system, but I am running in to a couple ... Clients login at clients.example.com. ... Employees login at ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Design Issue (Employee and Client)
    ... Clients login at clients.example.com. ... Employees login at ... First design issue: ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Sap
    ... Our employees work in several skills including Web Technologies, ... Business Analysis and Quality Assurance. ... clients are usually in the Telecom, Banking, Health Care and Insurance ...
    (soc.culture.indian.delhi)
  • Re: Missive from me jollidays
    ... Our employees work in several skills including Web Technologies, ... Business Analysis and Quality Assurance. ... clients are usually in the Telecom, Banking, Health Care and Insurance ...
    (uk.people.silversurfers)