Though it's not supported, the user did find a workaround to this problem:--Open the personal geodatabase up in Access > click open the GDB_ObjectClasses table > change the CLSID values for the tables from {F94F7533-9FDF-11D0-BEC7-00805F7C4268} to {7A566981-C114-11D2-8A28-006097AFF44E} then the Identify results will work in ArcMap.