The magix.info Community – Find help here
Forum
Tutorials
Media
Support
Sign in / register
Search ...
Help
Sign in
All
Forum
6
Tutorials
User
Media
All
Forum
Tutorials
User
Media
Options
Last year
Any time
Last 24 hours
Last week
Last month
Last six month
Last year
Video Pro X
25 answers, most recent on 2/11/2026
RE: Cannot start VPX17 by double-clicking on MVP file
@browj2 Hi John Did you try using a Macro with the RunApplication action instead of VBA and Shell. IMHO a much easier route. John EB
Video Pro X
25 answers, most recent on 2/11/2026
RE: Cannot start VPX17 by double-clicking on MVP file
@browj2 Hi John OT, however, It is has been in all versions since 2007. Click the Show all Actions when in the macro wizard The above is from 365, latest version, which I have to sort out the trust and security settings and being able to work
Video Pro X
25 answers, most recent on 2/11/2026
RE: Cannot start VPX17 by double-clicking on MVP file
@johnebaker @kPeiffer Hi John EB, Thanks for that. I didn't think to open the Show All list. I managed to get it working and have replaced the code in my database with dynamic code that opens VPX17 or VDL2026, depending on the selection in the
SOUND FORGE
31 answers, most recent on 4/17/2026
RE: Sound Forge alternatives
I’ve never used a program with an interface as clear and smooth as Sound Forge (same with Vegas), but their frequent VST plugin bugs—essential for audio work—plus High DPI issues (still in 2025!) made me switch reluctantly a long time ago. For
SOUND FORGE
31 answers, most recent on 4/17/2026
RE: Sound Forge alternatives
I’ve never used a program with an interface as clear and smooth as Sound Forge (same with Vegas), but their frequent VST plugin bugs—essential for audio work—plus High DPI issues (still in 2025!) made me switch reluctantly a long time ago. For
Video Pro X
25 answers, most recent on 2/11/2026
RE: Cannot start VPX17 by double-clicking on MVP file
@kPeiffer @johnebaker Hi, Thanks for your help. John EB, there is no RunApplication for macros in Access. @kPeiffer, your cmd code works fine outside of Access, but running it from within Access is done using shell and doesn't work. The workaround
1