>Bill,
>EXCUSE ME! I do have the source code! So if you are still interested in helping me out I'll be able to make changes as needed.
>Ed

Here is a 'jumping off' point...

1. Install FoxFire into a FF60 folder just beneath your application's folder.
2. Create a new project called FFLAUNCH with only 1 code file containing the following:

* launch the foxfire report generator with incoming userID

LPARAMETER tcParameter

LOCAL lcUserID

* condition parameter
lcUserID = IIF(VARTYPE(tcParameter) <> "C", "", tcParameter)

* set up environment
SET TALK ON
SET SYSMENU TO

* don't allow closing fox window (could be done better)
_SCREEN.Closable = .F.

* run foxfire
DO ("FOXFIRE.APP") WITH "REQUESTS", lcUserID, "", "FFCONFIG"

3. Compile this into FFLAUNCH.EXE and make sure a copy is located in the FF60 folder beneath your app.

4. Add a menu bar to your app (or command button) and drop the following code in the click event:

* exec the new foxfire launch program passing the userid

LOCAL lcExec

* change dirs down into FoxFire folder
CD FF60

* build launch line
lcExec = "RUN /N3 FFLAUNCH.EXE " + TRIM(goApp.oUserMgr.cUserID)

* launch foxfire
&lcExec

* cd back up to application directory
CD ..

As you can see, this code will change directories down into your FF60 folder and execute the launch program passing the current user ID. If you set up the users in both the MM app and the FoxFire app, they won't have to log into FoxFire.

Don't forget to either compile in a copy of CONFIG.FPW or have a copy in the FF60 folder with the MVCOUNT=2400 line in it. FoxFire uses a TON of memory variables and will not run without this line.

Once you have this working, you can look at other options such as sending a cursor of instructions to FoxFire.

Hope this helps.