WP7 .wcm files no longer executable after WP12 installation

[Cory Engel]

My workgroup has been using WP7 for years (7.0.2.45). We're going to be
upgrading to WP12 soon. I'm the guinea pig, mainly because I'm "the
macro guy" who writes the macros we depend on heavily.

When I installed WP12 on my computer, no surprisingly, it became the
default application for WP file types, including .wcm files. However,
during a transition period, I will keep WP7 on my computer and continue
to use it for macro execution. I used Windows Explorer to re-associate
..wcm and other WP files with WP7. However, now whenever they are called
in any way (double-clicking, Start Menu, toolbar button, etc.) they do
not execute, but rather open in WP7 for editing.

I then tried changing the associated application with PerfectScript 7
instead of WP7, but that didn't help either.

How do I change the behavior so that clicking a toolbar button or
double-clicking a macro file will cause it to execute?

I'm really looking forward to computing in the 21st century.

[lemoto]

Cory:

> When I installed WP12 on my computer, no surprisingly, it became the
> default application for WP file types, including .wcm files. However,
> during a transition period, I will keep WP7 on my computer and continue
> to use it for macro execution. I used Windows Explorer to re-associate

> ...wcm and other WP files with WP7. However, now whenever they are called

> in any way (double-clicking, Start Menu, toolbar button, etc.) they do
> not execute, but rather open in WP7 for editing.
>
> I then tried changing the associated application with PerfectScript 7
> instead of WP7, but that didn't help either.
>
> How do I change the behavior so that clicking a toolbar button or
> double-clicking a macro file will cause it to execute?

That association only tells Windows which file to send it to for editing,
which of course is happening.

If you will email me with a brief note reminding me of the issue I shall
send you a macro that can report the relevant registry settings, and change
them to suit v9. I think you will see how to edit it so that the pointers
suit v7.
To email: http://www.lemoto.myby.co.uk/relay.htm
--
Good wishes!
Roy Lewis
C_Tech volunteer
(UK)

[Cory Engel]

Thanks to lemoto for the solution here. Ultimately, the fix was in changing
the settings for PerfectScript files in Exploring > View > Folder Options >
File Types to the following:

Compile:
c:\path-to-PerfectScript-application\Ps70.exe /c="%1"

Edit:
c:\path-to-PerfectScript-application\Ps70.exe /e="%1"

Run:
c:\path-to-PerfectScript-application\Ps70.exe /# /m="%1" %*

Debug
c:\path-to-PerfectScript-application\Ps70.exe /x="%1" %*

[lemoto]

Cory:

> Ultimately, the fix was in changing
> the settings for PerfectScript files in Exploring > View > Folder Options
>
> File Types to the following:
>

Glad you have it fixed!
Thanks for the report.
That method does indeed avoid crashing around in regedit and perhaps making
a typo or two.