Column data incorrect when switching between databases #7099
Description
Column data is incorrect if the stored column order contains UDFC entries which don't exist in CUSTOMFIELD_V1. This may occur since SETTING_V1 is cross-database -- you can open db1 and the UDFC columns will be stored in the order, but when you open db2 which doesn't have any UDFC fields it still loads them into m_real_columns which throws off the order.