Bill,
Did you have the source code for FoxFire so you could make it an exe? Yes, I'm interested in knowing more detailed information about how you resolved this compatiblity problem.
Ed
>Ed,
>
>I have a very large app written with MM running FoxFire. After spending several hours trying to solve compatibility issues, I finally built FoxFire into a separate executable that I call from my MM application.
>
>I didn't find the support at FoxFire very helpful. I tried their suggestions concerning unloading classlibs and progs before calling their app. Nothing stopped the errors. FoxFire uses a TON of memory variables. (Don't forget the MVCOUNT=2400 in the config.fpw).
>
>I built a very small project that I use to build a separate .exe to launch FoxFire. It accepts command line parameters for my user and department. I call this .exe from a menu option and side-bar form button.
>
>I also wrote a second launch program that uses a file hand-off to automate FoxFire. I have a table that relates reports to forms in my app. The user can build a report in FoxFire, then tie it to a form or forms in the main app. The user can then tap a tool-bar button and select reports tied to the active form. The reports are launched in FoxFire, even filling in run-time query fields. It all integrates very cleanly.
>
>FoxFire's UI is a little loose, but it is an excellent tool.
>
>If you want more information about either of these methods, let me know.
>
>