Thanks Pamela and Larry for your replies. I work a lot with VFP and I didn't know that; when VFP8 was released I went to Microsoft web site and checked the features. It says that you need either Windows 2000 with Service Pack 2 or later, or Windows XP or later.

As it does not specify development and runtime versions, I understood you needed win2000 for both. They should be more specific in the web site; I did not update to VFP8 just because of that, and know I'm almost at the end of a large project and don't want to risk having problems in the upgrade.

Regards,
Javier.


>You can't develop VFP8 on Windows 98. The runtime is supported on Windows 98. I have 3 production apps compiled in VFP8 running on Windows 95. As long as you don't use any of the language features requiring the services of the later operating systems, your app will still run.
>
>pamela
>
>>you can't run VFP8 on Windows 98, so what do you do when a client has several win98 machines?
>>
>>>Why not move directly to VFP 8?
>>>
>>>pamela
>>>
>>>>Interesting. We're still using VFP6, though. We'll be moving to VFP7 soon (hopefully), and possibly soon after up to 8, so I'll keep that in mind. For now, I'm trying out setting the method (in this case, the INIT() method) to be Protected, so that the INIT() code won't be accidentally hidden. Instead, I created Pre_Init() and Post_Init() hooks. So far, that doesn't seem to cause any problems.