Perhaps you could clarify exactly what it is you're trying to achieve. I would have thought it illogical for your table to have just the 1st & 3rd rows completed, leaving the 2nd & 4th rows' fields empty. Certainly, a macro could be coded to take that into account, but there seems to be no end of possibilities for what might be done wrongly (eg someone leaves the first field empty, but fills in the others on the same row).

__________________
Cheers,
Paul Edstein
[Fmr MS MVP - Word]

macropod: "Elan05, while not LITERALLY true (there is - eventually - an end), macropod's comment does point out something very important. To make some of the things we want to happen, actually happen fully and accurately, can take a complexity of logic (i.e. "possibilities")...NOT programming. The actual code required is not always more complicated; there is just MORE of it, and the relationship between logical elements becomes critical.

For example, if it is logically important to retain information (say that row 2 does NOT have formfields), then it is 100% the responsibility of the coder to make that possible. VBA will not remember anything unless it is explicitly instructed to do that.

These are logical processes, and not essentially code processes. The code is pretty trivial. or prehaps it is better to say, simple.

The more you can think things it out - if I suspect something I am working on may be seriously complicated I actually write things on...gasp...paper - the better and faster you will get to where you want to be.

BTW, thank you for detailing what you are working on in multiple threads. Some times people ask too many things for a single thread.