>Right-o! NEVERNEVERNEVERNEVER zap is my motto. Well one of them anyway < s >.
>
>I imagine that that could cause some problems when doing a tableupdate sometime later that would fire the triggers. Dunno, offhand.
>
>>Which., of course, is still a major problem, since all the parent-child links are gone so all that remains is a bunch or orphans.

It's a one-for-all-'n'-all-for-one. If I zap something during development, I actually write a little .prg which zaps all interdependent tables in one package, leaving no orphans. Zapping one dependent table is just plain calling for trouble.