Not sure I understand how that will help since the "automatic" rebuild isn't able to fix that kind of error - unless you're saying 2019 has capabilities that 2016 doesnt?

I will hold on to this just a bit to see if there's another solution so thanks for the input.

Question though - if I load it in 2019, won't it upgrade the file?  How will I then open it in 2016 again?  We are not able to upgrade versions at this time and if memory serves once a file is upgraded, older versions can no longer work with it.

thx,