🚀 go-pugleaf

Remy Lebeau (TeamB)  wrote:

> "Adam Versteegen" <No@email.com> wrote in message
> news:3ef4140b@newsgroups.borland.com...
>
> > It seems odd that the openas verb would
> > return 'no association' seeing as thats the
> > whole point behind passing in 'openas'.
>
> It makes sense when you understand what is actually happening behind the
> scenes.  The "openas" verb is still a verb like any other, and as such
must
> still have the appropriate Registry settings in place to support it.  It
> turns out that the "openas" verb is associated only with the "Unknown"
> subkey, in other words is only for file extensions that don't actually
exist
> in the registry at all.  If you pass in a filename with an extension that
> does exist in the Registry but simply doesn't have the "open" and "openas"
> associations set up for itself, then that would explain the symptoms that
> you are seeing.  If, however, you pass in a filename with a truely unknown
> extension, then "openas" should be triggered correctly.

Hello Remy,

While that makes sense, its doesn't seem to be whats happening. If I attempt
it with a file with any random extension I have just made up (eg,
myfile.asdfasdf or myfile.pzz etc) it still comes up as no associate/unknown
association. Yet if I double click that file in explorer it brings up the
open with dialog.

Any more ideas?

Vesty.