Tag Example: http://screencast.com/t/Xwzd0mcgIQna
Results in Window: http://screencast.com/t/17o8vQXbT
I have come by a situation where there is a custom field on a window that was created in version 11 of Dex. Fast forward to the present and the current version is 14. When I opened the version 14 project I found that clicking on some custom text prompts showed the wrong values in the Properties window (see linked image "Results in Window"). I have come to discover the custom fields and/or text prompts added were assigned Tag values which were unique in version 11, but when the modifications were moved to version 14, new fields from Microsoft now used those Tag values and the UI is becoming confused. I can see this duplication by exporting the form to a text file.
I am unsure of the steps taken to move the custom resources between versions, so that can only be speculated on.
I have a process I use for upgrading custom dictionaries and I have never myself come across this issue in my own projects. However, I just tested that process starting with the version 11 dictionary of this project and it failed to prevent this problem.
Question : What I am wondering primarily is whether there is a process for "upgrading" the custom dictionary that reassigns tags which are now being used by new resources in the main dictionary. Or, is there reason to believe these resources should never have been assigned the Tags they have? I thought for a moment they would show in the Index file but they do not, so by my testing it appears the tags are not subject to the "greater than 22,000" resource ID assignment for custom resources.