>It shouldn't be that difficult to normalize/denormalize. It's done all the time.
>

Does this logic fit in with how you would approach it:

User displays screen for a location and week:
I pull out all the data from the underlying normalised table and massage it into how I need it.
User updates a couple columns in one row, adds a new employee row and deletes another employee row, then saves.
In the background I will have to:
- detect what was changed in the columns and update the underlying rows in my normalised table, (if there was no entry for a particular day I'll have to add that row in)
- then insert the appropriate rows for the newly added employee and
- then delete the rows for the deleted employee

Having not done this kind of coding in years, do I use GETFLDSTATE() to detect the changes and what type of change? Or is there something easier to use?