08-27-2009 08:10 AM
09-10-2009 08:09 AM
After talking with our ACT consultants, they verified that this is a bug in the system and were able to reproduce it in their lab. However, it didn't occur on the Remote Databases 100% of the time. SAGE was notified but was not able to give an explanation of this behavior and recommended recreating and redeploying the Remote Databases to the users who did not receive the new field names.
In my situation the first four users I checked didn't get the updates (including me), so I'm not looking forward to having to redo all of the RDBs. I'll only recreate the DB's for the remote users who really need to see these field names.
I'll post back here when/if I get an update.