PerkinElmer Informatics Support Forum
Decrease font size
Increase font size
Topic Title: Round trip editing broken Mac
Topic Summary: Round trip editing broken Chemdraw 17, MS Word 365, Mac High Sierra,
Created On: 12/16/2017 5:45 PM
Status Post and Reply
Linear : Threading : Single : Branch
Topic Tools Topic Tools
View topic in raw text format. Print this topic.
 12/16/2017 5:45 PM
User is offline View Users Profile Print this message


Posts: 1
Joined: 9/13/2010

Round trip editing just died in the last few weeks! On my MacBook Pro, running High Sierra, with Chemdraw 17 (specifically (131) shown in the "about" menu) and the MS word from Office 365 (version 16.8 (171210) in "about") I don't even get an image transferred when I copy and then paste into word. It looks like a SMILES string, but is too simple for the complexity of my graphics. With "paste special" I can force a graphic to be pasted, but it's dead upon return to Chemdraw. Pasting into Powerpoint (same Office suite) appears the same as "paste special" to Word: it does deliver an image that can scale (I think it's .pdf format) but is a dead graphic when I attempt to move it back into Chemdraw. Even old Word files where I used to be able to pull the image out and edit it now only give me a dead graphical block when I pick a chemdraw graphic out and pull it into the current version. Very frustrating. Since both tools have been updated in the last few months, I can't say which to blame.
 12/22/2017 3:08 PM
User is offline View Users Profile Print this message

PKI Ortega

Posts: 56
Joined: 10/13/2011

Please be aware that High Sierra (MacOS 10.13) is not supported by any version of ChemDraw at this point. The latest OS supported is 10.12.

The correct way to copy and paste in ChemDraw 17 and MS Office 2016 is to copy the structure from ChemDraw and then Paste Special > Paste as PDF into MS Word (or Excel or Power Point).

Then if you wish to edit the structure again you must copy it from your MS Office application and paste it back into ChemDraw (Please confirm if this is what you are doing).

Once again, this could all be caused by a non-supported Operating System.

Additionally version 16.8 seems to be an Office Insider (beta) version and not an official release for MS Office. That means that you are also using a non-supported version of MS Office


- PKI Support

Edited: 12/26/2017 at 3:17 PM by PKI Ortega

FuseTalk Basic Edition v4.0 - © 1999-2018 FuseTalk Inc. All rights reserved.