Create your new database.
Link the Worker table from the other database:
File | Get External | Link
Create a Skill table with fields:
SkillID Text Name of the skill (primary key)
Create a WorkerSkill table, with fields:
WorkerID foreign key to the WorkerID in the linked table.
SkillID foreign key to the Skill table.
Create a main form bound to the Worker table.
Add a subform bound to the WorkerSkill table.
In the subform, include a combo that has the Skill table as its RowSource.
In the subform, you can then select as many skills as apply to the worker in
the main form, one per row.
(This is a *way* better data structure than having lots of yes/no fields in
one table. For example you don't need to change the entire data structure
just to add one more skill.)
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"jh" <vc> wrote in message
news:43*********************@dread16.news.tele.dk. ..
The situation:
A database is wanted. It's purpose is to show some co-workers' skills.
Therefore I will need to make a database that contains names and the posts
"skill1", "skill2", "skill3" etc. (YES/NO-posts)
This should be easy; one table in a simple database, but...
In the company we already have another database containing the co-workers
work-ID-number and their names. I would like to use this existing
information in the new database, then we will not need to maintain another
database with names.
(and no, I'm not allowed to extend the already existing database with
skills)
Therefore; a new database which "collects" certain information from an old
database.
The new database must of course synchronise with the old, so the name
information always will be the same in the 2 databases, meanwhile the new
database can hold the "skill1", "skill2", "skill3" etc. to a certain
co-worker.
Hoping for some tips.
Regards
hansen
