Actually Dale, just FYI, those attributes *were* already set up
(AccountType in sa and matching record/field in RadATConfigs). That's what
stumped me, and I fired off the note above 'just in case' while continuing
to create the tables that are new in 2.5 and populating the new field
additions to our preexisting tables from v1.16.49b. After that was done
everything worked fine, with no need to add any attributes (they were
already there, including defaults). Seems that it must have been a
different relationship that was dependant on one of the new changes that
was triggering the errors.
(Sorry if my note was yelling fire prematurely, but being down on a busy
weekend with phones ringing off the hook is no picnic, as I'm sure you
know. Just wanted to get the question out there as a backup plan in case
what we were doing still didn't solve the problem.)
Thanks,
-Ted