>
>Ok guys, you're on a roll... It's not necessary for what I'm doing at the moment, but how would I tweak the the code to return the alias and field name for the non-matching fields? ...and what if there are more than one?
>
>Renoir

In that case, instead of returning a logical, I would return an object with an array property with all the fields in alias1 that didn't exist in alias2. By runnig through the arrays again, you could just as easily get the fields that exist in alias2 that don't exist in alias1.

If everything matched pass back a NULL and check for that. If everything didn't match, the calling routine would receive an object and would need to parse the aFieldsThatDidNotMatch array property.