Sorry, was away from my desk...

I'm not exactly sure, yet. This is all very much in the design stage. I'm trying to break down different types of tasks. I will have one main table that holds stuff like who the task is assigned to, when it was started on, what its status is.

The child table(s) will be memo fields and characters. If the task is, say, documenting, I may just have a character field saying what I'm documenting. If the task is adding a field to a screen, I'll need stuff like what screen, field name, control source, etc.

Or, I could just have one memo field called "task" and shove it all in there. But I'm trying to get away from the free-form style into specific forms to fill out with different fields for each form.

It's still all really nebulous. I'm just trying to get ideas down right now.

Thanks,

Michelle



>It sounds like it would help to quantify it more. Roughly how many possible different children, and how different is the data for each?
>
>Obviously you don't want hundreds of tiny child tables, but neither do you want one table with a zillion fields hardly ever filled. Can you organize the possible situations better?