Is this reproducible if you create a small test file with the field located in the same location? For such a test create a brand new file from scratch and do not copy and paste anything into it from your existing file. You need not reproduce your entire file's design, just add enough details to reproduce this one issue.
This test is to rule out any possible corruption of your database file. The fact that it worked fine in 11 does not guarantee that the file is not damaged. The damage may have occurred after the conversion or the damage was such that it didn't cause a crash in 11 while it does in version 12.
Hi Phil! I did create a new file and conditions, but that file did not have the problem.
On the file with the problem, I've tried:
Recovering the file - no errors reported, still crashes
Deleted the field and placed a new field on the layout - still crashes
Deleted the value list and field and recreated it - still crashes.
I've tried re-converting the file, same problem.
I'd hate to have to delete the whole layout, tons of work to re-create it...
If the new file can't reproduce the issue, this suggests that your file is damaged. You might try recovering the file in it's pre-conversion format, then converting the file.
Things to keep in mind about Recover:
While Recover almost always detects and fully corrects any problems with your file...
- The recovered copy may behave differently even if recover reports "no problems found".
- Recover does not detect all problems
- Recover doesn't always fix all problems correctly
- Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.
And here's a knowledgebase article that you may find useful: What to do when your file is corrupt (KB5421).