Hello Edward,

No apoligy necessary. Your advise/suggestions are more than welcome. You and Nancy have provoked me to rethink an app I designed in crisis more than three years ago in another language.

I referred to my old notes and read that the user claimed that most of the employees had many liceneses. Understandable since a RN may have a license for each state in this area: MD, VA, DC. The data for each license being unique. He/She may also have other licenses: LPN for instance. And since there are only 150 employees in these little companies, I took the easy way - one less table. Actual all the employee data was in one table originally.

After reviewing the actual data I find that very few employees have multiple licenses. None have as many as five. Hence a table containing the skill data would delete 20 fields from the employee skills table and may have only one child record for most employees and have the advantage of containing an unlimited number of skills for any employee. I just have to replace the twenty fields on the PageFrame Tab with a grid because the expire dates and registration numbers change sometimes yearly.

The PageFrame Tabs for the employees are: Personal data, Preference data, Skills data, Notes, Grid/picklist, TaskOrders(one to many) and in the future a traning tab (one to Many) for the quarterly training home health aids must complete.

A similar PageFrame is used for the Patient, Clients, Diagnosis, Notes, PickList, TaskOrders.

An excellent example of the amount of effort that goes into designing an app regardless of how many records are involved - 100 or 100 million.

Thank you both.

Regards,

Paige