Re: Changed MDI file Association to Acrobat Reader by Bob
Bob
Fri May 02 08:51:41 PDT 2008
Logic question. Why would you want to "associate" .MDI with the "writer"
in the first place anyway, it doesn't open it, it creates the file, it
doesn't need to be associated? It's a "virtual printer". It's the
"Viewer" that you use to open the file, that's what needs to be
associated.
Pappy wrote:
> I found the solution. When I installed the "viewing" portion of "Microsoft
> Document Image Writer" it re-associated the file extension automatically.
> Why would MS split the application like that? One app to create a .mdi file
> and another to view it? Seems down right silly to me.
>
>
> "Pappy" wrote:
>
>
>>I have an end user who was trying to open a MDI file. It would not open
>>because Micorsoft Document Image Writer was not installed. My little end
>>user decided that it could be "opened with" Acrobat Reader so he tried that
>>with the option to "always use this program" when opening this type of file
>>selected. When that didn't work he asked me to fix it. Now that I've
>>installed the MDI options for him I need to associate the .mdi files with the
>>Microsoft Document Image Writer program again. Does anyone know which file
>>(.exe) I should tell Windows to use to open these types of files? He is
>>using Office 2007. Thanks for any help.