Associate an Empty File Extension?

How can I enable Vista to recognize filenames that have no extension as
WordPerfect files?

Has anyone out there been able to make Vista associate un-extensioned
filenames with *any* particular application?

Brian

--------------------------
Background:

XP allows it. One of the Vista Betas allowed it.

I name my WordPerfect documents without file extensions, e.g. "122046"

From within WordPerfect, if I ask WordPerfect to use nothing as the default
file extension for WordPerfect documents, WordPerfect displays an error
dialog stating that although you *can* set WordPerfect to do so, Vista will
not recognize such non-extensioned filenames as WordPerfect files, which is
true. (The resulting icon for a WP file looks like a blank piece of paper.)

I know there are some system files without extensions, but I keep my WP
document files segregated, so under XP (and under that Vista Beta), when I
saw a non-extensioned filename with a WP icon, and it wasn't where my WP
files lived, and it wasn't named using my WP-document naming convention
(6-digit numbers), then I immediately knew that it was a system or other
file. (And I saw very few of those files.)

Thanks for any and all pointers.

The file extension is what creates the association so , NO - I don't think
you can associate a file without an extension.


--


Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)



"Brian Bradley" <brian(HYPHEN)> wrote in message
news:%...
> How can I enable Vista to recognize filenames that have no extension as
> WordPerfect files?
>
> Has anyone out there been able to make Vista associate un-extensioned
> filenames with *any* particular application?
>
> Brian
>
> --------------------------
> Background:
>
> XP allows it. One of the Vista Betas allowed it.
>
> I name my WordPerfect documents without file extensions, e.g. "122046"
>
> From within WordPerfect, if I ask WordPerfect to use nothing as the
> default file extension for WordPerfect documents, WordPerfect displays an
> error dialog stating that although you *can* set WordPerfect to do so,
> Vista will not recognize such non-extensioned filenames as WordPerfect
> files, which is true. (The resulting icon for a WP file looks like a blank
> piece of paper.)
>
> I know there are some system files without extensions, but I keep my WP
> document files segregated, so under XP (and under that Vista Beta), when I
> saw a non-extensioned filename with a WP icon, and it wasn't where my WP
> files lived, and it wasn't named using my WP-document naming convention
> (6-digit numbers), then I immediately knew that it was a system or other
> file. (And I saw very few of those files.)
>
> Thanks for any and all pointers.

If you know "for a fact" what the extension was, or should be - just rename
the file and give it the correct extension. Then the associated program will
open when you click on the file.

--


Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)



"Brian Bradley" <brian(HYPHEN)> wrote in message
news:%...
> How can I enable Vista to recognize filenames that have no extension as
> WordPerfect files?
>
> Has anyone out there been able to make Vista associate un-extensioned
> filenames with *any* particular application?
>
> Brian
>
> --------------------------
> Background:
>
> XP allows it. One of the Vista Betas allowed it.
>
> I name my WordPerfect documents without file extensions, e.g. "122046"
>
> From within WordPerfect, if I ask WordPerfect to use nothing as the
> default file extension for WordPerfect documents, WordPerfect displays an
> error dialog stating that although you *can* set WordPerfect to do so,
> Vista will not recognize such non-extensioned filenames as WordPerfect
> files, which is true. (The resulting icon for a WP file looks like a blank
> piece of paper.)
>
> I know there are some system files without extensions, but I keep my WP
> document files segregated, so under XP (and under that Vista Beta), when I
> saw a non-extensioned filename with a WP icon, and it wasn't where my WP
> files lived, and it wasn't named using my WP-document naming convention
> (6-digit numbers), then I immediately knew that it was a system or other
> file. (And I saw very few of those files.)
>
> Thanks for any and all pointers.