It's still not there. And you are right, there is a whole lot left to be desired about ERwin. The glaring lacks are shocking really, given the software cost.

That said, I do use those domains/data types that you talk about, and it really helps a lot--not only for creating consistently defined fields across tables, but also when writing stored procs and functions. There are also other aspects that I like about having a professional data model, both at the beginning of the project and over time. I appreciate your tips for how to make RAP work with ERwin.

Thanks again for sharing. You sure are putting yourself out there and taking a lot of you-know-what for it. Takes courage.