OK, look:

1) Win98 is not going to work for you in your build. I think I already told you that, but maybe I didn't say it clearly, so I'll say it again:

* -- Win98 is supported for VFP only for distributed applications, BUT

* -- there were a number of issues for using the reporting components in the beta build on Win98, that have been fixed now. Quite a few scenarios involving REPORTOUTPUT.APP WILL NOT WORK, no matter what you do, as far as setup goes.

So you can forget about testing in Win98 in your build. You need to be patient about this, there are just too many things that needed additional work after the public beta build for me to list them here. Most of them, yes, have something to do with the way we address GDIPLUS.DLL, but you cannot fix this just by copying over a newer GDIPLUS.DLL into your Win98 system. It had to be fixed in VFP <s>. OK?

2) Your CONFIG.FPW says the following:

_REPORTPREVIEW="reportpreview.app"
_REPORTOUTPUT="reportoutput.app"

This probably will NOT WORK either <s>. You have not pathed the references. I can't tell where your current directory is (CURDIR() for your application inside VFP) but at the time your CONFIG.FPW is read there is a very good chance that this is not correct.

If you install the applications (all three of them) with a distributed application, by default, VFP will look for them in HOME(). HOME(), for a distributed application, means where the runtime DLLs are. NOT where your EXE is.

So your choices, if you wish to deliver the apps separately, are:

* -- put the REPORT*.APPs in the same directory as the runtime DLLs. (usually c:\program files\common files\microsoft shared\vfp or something like that). There will be an MSM delivered with the product that you can use in your InstallShield project, to handle this, if you like.

* -- put the REPORT*.APPs in some other directory belonging to your application. Put fully-pathed entries pointing to these files in your CONFIG.FPW.

* -- put code in your application pointing to the proper locations of these files, just as you would point to any other external apps.

You can also bind the components of the apps directly into your applications. I don't think this will work properly in your build, either, but it will in release. There will be documentation explaining this.

HTH,

>L<