It sounds like you've run into a bit of a variant of a couple of [URL="http://www.monarchforums.com/showthread.php?t=3454"]other problems[/URL] regarding [URL="http://www.monarchforums.com/showthread.php?t=3518"]exporting to Excel[/URL].
In your case, I've built a test to duplicate the difficulty that you've described. I suspect, but will leave to you to confirm, that in the case of your item #1, you're attempting to append data to an existing worksheet.
In my test, I was able to get the "export successful" message and see that in fact no new data had been appended to the existing worksheet. I was only able to accomplish this following these steps:
Monarch exports to Excel workbooks using Excel's named ranges. When someone opens Excel the workbook file and just clears the contents of the cells, without deleting the rows, this negatively affects Monarch's append exports, which Monarch reports as successful. Full overwrites of the worksheet won't be affected.
As mentioned in one of those other threads, the best solution is to not manually modify sheets that Monarch creates/uses. Doing so is just looking for trouble with your Monarch exports.
Regarding your problem #2, when exporting to workbooks that contain references to the values that Monarch exports, the [URL="http://www.monarchforums.com/showthread.php?t=3141"]current solution /URLis to use Excel files that contain macros, and have a macro automatically issue an Application.CalculateFull command upon opening the workbook.
No, it's not the optimal solution, but until this is resolved by a patch release or the next full version of Monarch, it's what we have available.
These are solutions that have been adopted successfully by others, and I'd encourage your group to do the same (for now) and not give up on a lot of positives in the v10.5 upgrade because of these workaround solutions.
I agree, it sounds like a name range issue for #1.
On the 2nd issue, this worked previous to the upgrade? The only reason I ask is editing a file outside of Excel typically will only update the fields that are being updated and not other fields that are referenced. Data's solution would have the best outcome and help prevent any other fields not updating correcting.