In our program the users can double click on a list of files and we 
shellexecute "open" to open the file. One customer has one windows 2000 
workstation out of six that is having problems where the file isn't 
opening. We get back an error saying "no program associated". However if 
we double click the file in windows explorer it opens fine. We found 
many copies of shell32.dll on the computer and so we removed all but the 
one in winnt\system32 folder and one in the folder 
winnt\system32\$ntuninstallkb890047.

After doing that now that workstation can open most files from within 
our program except .PDF files.

No other workstations have the KB890047 security patch installed.

Any ideas? Our application is written in D6.

Daniel

> After doing that now that workstation can open most files from within 
> our program except .PDF files.

I have found in the past that PDF files are notoriously sensitive to
the arguments you provide in your ShellExecute call.

Try playing around with the last argument - try
SW_SHOWDEFAULT instead of SW_SHOWNORMAL, or vice versa.

Most programs ignore this anyway, but Adobe apps work with
some, but not other, window state arguments.

Try this in addition to Remy's suggestion above.

cheers,

Chris

"srdaniel"  wrote in message 
news:477552e3$1@newsgroups.borland.com...

> One customer has one windows 2000 workstation out of six
> that is having problems where the file isn't opening. We get back
> an error saying "no program associated".

Then the extension of the file bing clicked on does not have an "open" verb 
registered for it.  Not all extensions use "open".

> However if we double click the file in windows explorer it opens fine.

Double-clicking a file in Explorer does not force the "open" verb to be 
used.  It uses whatever the actual default registered verb is.  To execute 
the default verb when calling ShellExecute(), specify a NULL verb instead of 
a hard-coded "open".


Gambit