Gary;

I think what this all boils down to is what does your corporation use as a “standard” and what do your clients use? Backward compatibility has a cost as does not supporting a previous operating system. So I would think that the market of Microsoft products in this case is driven not by a “new version” but rather the needs of customers.

Granted software will be purchased (upgrades) by developers when VFP 8.0 comes out but the question is how many clients will hold back using such a product or any product that requires major and costly changes from what is presently in house and functional?

Budgets are very tight here in Silicon Valley where you do not know from one day to the next how many more companies will fold or the number of employees laid off. This area for one is not going to be a “shining example of sales” of Microsoft’s producing new software in poor economic times.

Tom


>Hi Joel:
>
>PMFJI but as far as I can ascertain, the (main) reason for not supporting Win95/NT with VFP8 is that neither of these versions of Windows provide active desktop support. VFP8 uses a different graphics API to support XP/Themes which by default, appears to rule out Win95/NT, rather than a specific business decision just to deliberately exclude these Windows versions, per-se.
>
>Best
>
>>Hi John,
>>
>>I know that MS announced a while back that Windows 95 is no longer supported. I assume this is why we don't see it as a target for new MS products. Has the same announcement been made about Windows NT4?
>>
>>Thanks.
>>
>>>Not supported.
>>>
>>>>
>>>>>You can create and distribute run-time applications for Windows 98, Windows Me, Windows 2000 Service Pack 2 or later, and Windows XP.
>>>>
>>>>And Windows NT too? (please??)