Jon -

Have you upgraded to Sage 50 2016 yet? Does it have the same conflict with eClinicalworks? I have been running Peachtree 2012 in an XP VM on my Win 7 Pro client. I'll update to Sage 50 if I can run them on the same PC as eCW (not in a VM). Otherwise, I'll be switching to QB.

Thanks,
Greg

I forgot to mention that we are using cloud based eClinicalworks now vs. local server in case this makes a difference.

-Greg

I don't think cloud vs local makes a difference since ECW is still installed locally when using the cloud-hosted option.
We've had this issue with every single peachtree update, including the update to 2016. It has not been a huge problem for us, since the "fix" I posted above still works!

The drawback is that it has to be run each time Peachtree is updated (the main program, not when updating tax tables, etc). Since peachtree is updated on each workstation, the fix must be run there as well. We only have a small number of PCs that run peachtree, so it's not a huge deal for us to just run that script after updating peachtree since we(admins) have to install it anyways.

If you have a ton of users that run peachtree, or have end users installing peachtree updates, that would be another story.


tl;dr - Sage still breaks it but the fix works -

Regarding Err 438 message while logging in eCW

Run below script from an admin cmd
cd "c:\program files\eClinicalWorks"
(or "c:\program files (x86)\eClinicalWorks" for 64-bit OS)

for /r %i in (*.dll) do regsvr32 /s "%i"

I'm the only one who runs Sage, so the fix is doable. Thanks for the speedy response!

-Greg

Not a problem!
I forgot I subscribed to this thread. I'm glad I could help!