I have a form with a zillion fields on it, most of which are in a tabbed table. We’ve made some changes, so that after 1/1/14, some of the fields will disappear and things will be renumbered, etc. So to do that and maintain backward compatibility, I’ve decided to move (cut/paste) that tabbed table to a subform. Then I created a new subform and pasted the same tabbed table into it and made the changes. Then the original form (which used to have the tabbed table) now has a computed subform. The formula is @If(RecdDate >= @Date(2014;1;1); “App-Sub”;“App-SubLegacy”).
I open a document with a RecdDate of 1/1/2013, I see the legacy subform. I edit that document change the RecdDate field to 1/1/2014, save it, and open it again, I see the new subform. Now here’s where it gets weird…I then edit this same document making no other changes than setting the RecdDate back to 1/1/2013. When I try to save it, I get an Input Validation error on one of the fields (length>18). I look at the field and some times it’s filled with gibberish. Granted, this is not how the application was intended to be used, but it’s very odd behavior. Anyone else seen anything like this before?