jonnyboy81
New member
- Local time
- Today, 04:28
- Joined
- Dec 8, 2014
- Messages
- 5
Hi Guys, I'm a pretty novice user of Access. Thought I knew what I was doing until I tried to created a complicated contact database.
I'm trying to set up a DB with hundreds of contacts, which I want to be able to sort via two main fields. Functions and Specialisation.
'Functions' is more or less a department field but as there is crossover I need to be able to add multiple 'Functions' values for each contact.
'Specialisation' narrows down departments into sections but again as there is crossover so there needs to multiple 'Specialisation' values.
I originally thought having two tables 'TblFunction' & 'TblSpecial' listing all the values I need (linked via the Function PK) and having two fields on my 'Contacts' Table (where I store Names, Phone Numbers etc) as a Lookup Fields would be all I need but I have since learned this causes a number of problems when running queries etc.
Is there a better way to store multiple values in a field or am I better off trying to break each table down into more tables?
I had thought about putting in multiple fields as check boxes but it works out as way too many fields and became pretty unruly pretty quickly.
Any advice no matter how small, even to point me in the right direction, would be greatly appreciated.
J
p.s. sorry if I didn't explain this very well!
I'm trying to set up a DB with hundreds of contacts, which I want to be able to sort via two main fields. Functions and Specialisation.
'Functions' is more or less a department field but as there is crossover I need to be able to add multiple 'Functions' values for each contact.
'Specialisation' narrows down departments into sections but again as there is crossover so there needs to multiple 'Specialisation' values.
I originally thought having two tables 'TblFunction' & 'TblSpecial' listing all the values I need (linked via the Function PK) and having two fields on my 'Contacts' Table (where I store Names, Phone Numbers etc) as a Lookup Fields would be all I need but I have since learned this causes a number of problems when running queries etc.
Is there a better way to store multiple values in a field or am I better off trying to break each table down into more tables?
I had thought about putting in multiple fields as check boxes but it works out as way too many fields and became pretty unruly pretty quickly.
Any advice no matter how small, even to point me in the right direction, would be greatly appreciated.
J
p.s. sorry if I didn't explain this very well!