John V. Petersen writes:

> I see you have answered my question here...

>

> So, you can't print.... Doesn't this effectively knock this out as a

> viable alternative???

I didn't say you can't print, just that its a pain in the ass (currently)=

to=20

set it up. This is all experimental stuff, not ready for prime time.

> With respect to ActiveX controls, and the lack of support, that makes i=

t

> a non-starter too...

Well... only if you rely on ActiveX controls. I always thought that Activ=

eX=20

was a pain in the ass to maintain so I avoided it like the plague. I've m=

et=20

a few others that have followed the same advice.

And... just because ActiveX doesn't work right now, that doesn't mean it=20

won't work in the future. Same goes for HTML help. The Wine folks are=20

writing their own HTML Help viewer based on either Mozilla or KHTML=20

(Konqueror). They'll likely eventually get ActiveX working as well.

> <<

> however, its a simple matter to copy over your EXE along with

> the VFP8 runtimes (vfp8r.dll, vfp8renu.dll, and msvcr70.dll).

> <<

>

> Looks like a EULA violation to me...

Perhaps it is, I really don't know. Nothing has been clarified for me in=20

this regard. I'm currently learning other languages and will wean myself=20

from VFP development but will continue telling people how to get VFP/Linu=

x=20

working until I'm told specifically to stop it.

> Well...at least it is on record now as an admission....

An admission of what? I never proposed the VFP/Wine thing as a viable=20

solution for the masses now. Just as a heads-up/preview of what we'll be=20

able to do a year or 18 months from now as Wine matures.=20

--=20

Paul McNett