> (I suspect I should have asked this question before
> spending hours doing what I'm now ask about).
[quoted text clipped - 28 lines]
>
> Thanks in advance for your thoughts.
Take a look at one of the pre-made databases.
File > New > Templates on My Computer > Databases > Contact Management
Might be just what you need and it's ready to use.
gls858
George - 27 Apr 2005 23:32 GMT
Yes, I looked at those.
You might call this an exercise.
I'm trying to emulate the Outlook Contacts form using
Access. Do you care to speculate on how Outlook lays out
its table (or tables) based on my question, b), below?
>-----Original Message-----
>> (I suspect I should have asked this question before
[quoted text clipped - 36 lines]
>gls858
>.
Outlook appears to use a 'flat file' data design rather than a 'realtional
design'
A better design is
(1) Contact has (Many) addresses (home, work, vacation cottage, villa in
Tuscany, etc)
(1) Contact has (Many) telephone numbers (home, work, home cell, office
cell, work fax, home fax, answering service)
(1) Telephone Type has many telephone numbers
(1) Address Type has many addresses
So we should have at least the following tables
Contacts (ContactID [primarykey], firstname, lastname, other stuff about the
person)
Contact_Telephones(ContactTelephoneID [primaryKey], ContactID [foreign key],
TelephoneTypeID [foreign key],Number,(maybe precedence order desired to
call)
Contact_Addresses (ContactAddressIDprimaryKey], ContactID [foreign key],
Address_TypeID [foreign key] , AddressLine1, AddressLine2, City, State, Zip
(for United States, may vary if you have to handle UK or European addresses)
Telephone_Type (Telephone_TypeID [primary key], Telephone_Type)
Address_Type (Address_TypeID [primary key], AddressType)
Then a set of forms to maintail all of the above.
Then a set of reports to print out a personal phone book.
Ahhh, also may want to handle email addresses and/or web pages and/or
............. :>
Hope this helps
Ed Warren.
> (I suspect I should have asked this question before
> spending hours doing what I'm now ask about).
[quoted text clipped - 28 lines]
>
> Thanks in advance for your thoughts.
George - 27 Apr 2005 23:47 GMT
Thank you, Ed.
Very thorough consideration
That will be helpfull
George
>-----Original Message-----
>Outlook appears to use a 'flat file' data design rather than a 'realtional
[quoted text clipped - 66 lines]
>
>.
John Nurick - 28 Apr 2005 06:47 GMT
>Outlook appears to use a 'flat file' data design rather than a 'realtional
>design'
In addition, there's a complicated relationship between the many
"fields" that Outlook exposes in the user interface and its object
model, and the rather fewer fields that it actually stores. When you
edit one field in the user interface, Outlook is often actually parsing
what you type into different underlying fields - and not infrequently
doing it wrong. Not a model to be emulated, IMO!
--
John Nurick [Microsoft Access MVP]
Please respond in the newgroup and not by email.