I'm sorry, but I don't see how the article relates to the *ambiguous* error that I am getting. I've encountered the schema error before, but I don't think this is related. I certainly appreciate your suggestion, though! 🙂

So far, I have re-built a new package, turned off (and on) all of the copy properties in turn, and I am now turning off the 110 (not 40, as I mentioned before) objects that contain at least as many ***********s as the error...so far no luck.

It's just frustrating that I had it working and all the sudden it's not. And if I had more of "something to go on" with the error, it would help. Even week-old data that had worked before doesn't work now (so I'm not sure if it's even an object causing the error).