>ed,
>i'll investigate further. another question if you don't mind, same app, different windows 95 machine, runs ok if i run it
>from the main form within vfp6. i install the app on the machine as standalone exe runs but am receiving
>fatal exception code = c0000005, i know this is a dcom95 issue, i've run into in the past and had to install dcom95,
> did same for this problem but it did'nt correct it. the app was built using vfp6 sp3. any clues.

DCOM is one of several things added to Win95 after it was released. What ActiveX Controls or other COM objects (things like Shell.Application, which relies on some components which only would be there if the Active Desktop components were added, or the Windows Script Host, or IE for the WebBrowser control) do you use - that should tell you what isn't present, and you can work backwards from there to figure out what needs to be added.

In some cases, you may find that it's a reliance on a specific version of a control rather than the one on the target system - for example, different versions of the ListView or TreeView ActiveX control might be the cause - superficially, the control is installed, but it may not be the one you need.

One of the most useful tools for tracking this down is the DEPENDS.EXE program that ships with Visual Studio and the NT Resource kit - it can examine executables, DLLs and OCXs and tell you what other files it relies on.