>>Michel, thier page says that the test version requiers the VB developer environment to work
>
>Yes, but it's a standard OCX. The only restriction is what they've included as an environment detector. There's no reason for them to restrict the OCX for VB only.
>
>>I (just) sent them email asking if their controls can be used with VFP5.0 and if I can
>>test that - I suggest you do the same
>
>This is what I've done this afternoon. Now, they'll have two. Maybe more can do the same as well. I've heard they have the best Internet OCX around.

I'm not sure, but I think you are talking about Crescest / Progressive ?
I have had several contacts with them re: MSComm32 / PDQcomm. Some information from them, and some others, indicate that there are some standards issues that have not been resolved with OCX (Active-X).
One of these has to do with *self registration*, which appears to be required by FoxPro. VB on the other hand does not *Require* self registration. Crescent stated in an e-mail to me that their controls are tested under VB, and *should probably* work in FoxPro, but that it could not be counted on. Also, if they did not work under FoxPro, then their technical support could not address this, although the control could be returned for credit.

I think you are correct, the more contact we have with them, and other OCX developers, pushing for FoxPro compatability, the better off we will be.