File extension association doesn't work - workarounds?

[inews]

I run a program which uses a particular file extension (say *.abc).
Opening files from within the program is perfectly functional.

However, by default, there is no registered file type for *.abc. When
I register the file extension to the relevant executable, and double
click on a data file, nothing happens.

The software vendors cannot help, not even to suggest the workaround
which I eventually stumbled across.

There is a workaround - add the executable to the "Send To" list,
right click on a file and the file opens inside the program as hoped.
The other workaround is to use an automation program, but is rarely
applicable.

I do this hundreds of times a day, so double clicking would be far
preferable.

Does anyone have a tip or a method to help with this?

What I have in mind is to create a New Action for "open" for the
particular file extension. The "Application used to perform action"
would then be the Shell or "Windows Explorer" used with suitable
switches to mimic the action of "Send To".

This may or may not be workable, so any suggestions will be welcomed
with open arms.

 

[inews]

Nevermind, though thanks. Found this on MSDN - http://support.microsoft.com/kb/241165

The basic idea is to use a variable to send the data path to the proc.

So, New Action, set "Application used to perform action" to
"<path>.exe" "%1"

The software vendors were very precious about the location data was
stored for the app, so maybe they didn't want it to work this way. Or
they were clueless... equally likely I think.