Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Row buffering
Message
From
28/01/1999 16:36:05
 
 
To
28/01/1999 16:29:12
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Title:
Miscellaneous
Thread ID:
00180821
Message ID:
00181554
Views:
8
>Hello Nancy,
>
>Thanks for the advice and suggestions. I/we need to be challenged to rethink/justify our original design from time to time. It can be a usefull exercise. I will think through this again.
>
>FYI there are 5 skill codes: HHA, COMP, RN, LPN. Can't remember the other. Only the codes, not the description, are kept in the record. The expire dates, registration numbers and areas in which they are valid are unique for each skill, for each employee.
>
>For instance I my have a Companion license valid in the state of MD expiring 2/01/99 no.123456789 and another Companion valid in the state of NY with a different expire date and no. I may also have a LPN license etc. the only thing common is the description which I don't store.
>
>Since an employee can have more than one skill I have five sets of fields in each record. The Skill codes and defination are loaded into an array for a dropdown/listbox but again only the code is stored.
>
>I really do appreciate the time you have spent with me.
>
>Regards,
>
>Paige

Sorry for jumping in.
It seems that you can split Skill table, but not as child. Actually, you have many-to-many relationships between Employees and Skills and it assumes that you need in mediator table between this too, i.e. you will get one-many-one (Employee-EmployeeSkill-Skills) structure. This EmployeeSkill table will contain foreign keys to both Employee and Skills and also all date, state etc. fields.
Edward Pikman
Independent Consultant
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform