Database Design Best Practices?

I've been tasked with normalizing a database currently in Microsoft Access 97, into a 3NF representation. I'll also be designing translation rules to migrate data from the non-normalized DB to the new 3NF DB.

I've studied DB design (classes in actual database theory), as well as physically done this before on smaller scale DBs where I already knew the DB thoroughly (i.e. I was the DB's creator). Now, this DB in question was not my creation, so I must go a little more slowly than I am use to with respect to normalizing, etc.

With all most 50 tables in the DB, I need a process and a plan to successfully do this, now more than ever! With smaller DBs, I always have a plan, but it is much more flee flowing. I really need advice on "best practices" for DB normalization.

Any document templates, processes, what should I take note of, etc would be greatly appreciated. I know the things I will keep track of, but if anyone has experience doing this sort of thing, I would appreciate any advice on what I should keep a detailed record off.

The people I am doing the work for don't really understand the scope of the task they asked of me, so of course I will be educating them as well.

Best practices? Doc templates? Ideas? Process? Any help is appreciated. I'd be more than happy to repost my findings to the group as a sort of "summary" of DB design best practices when (if) I get responses.

Thanks for your help.

--
Mike Loll
michaelloll_at_hotmail.com