Excel Graphs Change Size After Pasted as Link into PowerPoint
When pasting Excel graphs into PowerPoint as a linked object, the Excel graph will shrink to 50% size or grow to 150% size if any change is made to the Excel file it is linked to (in our experience, the object shrinks ~90% of the time). The dimensions of the object change in PowerPoint, but the scaling remains at 100%. In order to return the linked graph to the correct size as created in Excel, all Excel worksheets need to be closed and the 'Update Link' needs to be selected after right clicking on the graph. The linked graph will then grow or shrink to the correct size.
Scaling remains at 100% throughout this process unless the size is manually changed in PowerPoint. If the graph is resized in PowerPoint and then the graph link is updated, the graph will change to the size of the new scaling relative to the correct dimensions (i.e. if the graph was 2x4 in Excel, shrunk in PowerPoint to 1x2, and then was manually changed back to 2x4, the scaling would be at 200% so when the graph was updated, the graph size would increase to 4x8).
Below is a post in another forum that describes this problem happening to all metafiles pasted into PowerPoint:
"I draw charts in Excel and paste them into PowerPoint presentations, typically as Enhanced Metafiles, which has never posed me a problem with previous versions of PowerPoint.
However, in the latest version when I paste a chart as a Metafile / Enhanced Metafile its height / width become ~30% larger than the Excel original. Why? This does not happen when it is pasted in as a PNG / JPEG / GIF / Bitmap - the dimensions stay the same.
This problem does not apply in Word 2016 - the paste sizes are the same regardless of format"
Jim M commented
Same issue. I want to use EMF's for vector quality, but the sizing changes even when copy & pasting graphics between tabs in the same workbook.
Paul M commented
This problem also occurs in Word. I spent 8 hours on the phone with 3 levels of support and they finally acknowledged the bug. They are apparently working on it. I will forward this to the tech support rep I am working with.