Cindy earlier pointed out option 2 that you gave and that is probably
the road I am headed down. I would however, really like to hear the techincal reasons that win95 and wts4 cannot be supported. I'm not saying there is some big plan at ms to get all of us to buy an upgrade :), I just honestly would like to know the reasons.

>I understand your pov, but lets look at the other side of the story. If MS would have included Win95 in it's supported platform, you will admit with me that it would have needed more time to develop and test VFP 8. This would mean either:
>

The launch date will be delayed and/or
>

They would have to reduce the number of new features and/or
>

The price of VFP 8 would increase
>
>Now, why me, who use Win2K and have no machine with an OS older than Win98, would have to suffer these inconveniences because a minority of users like you need to support Win95? (I assume, maybe wrongly, that Win95 users are in minority).
>
>If support for older OS is a high priority, you can:
>

Stick with VFP 7
>

Go with VFP 8, but develop in a way that your code still compile in VFP 7 (you do not use VFP 8-only features or you brace them with #IF ... #ENDIF directive)
>

Use another language that is more portable (like C++)
>

Have a web interface so that the only requirement on the client is a browser
>
>>I think you're misunderstanding the situation. Our focus is not the desire to stay with windows 95. Our focus is to make 20 or so pentium 266's with 64MB and windows 95 last as long as possible. That means as long as they run our software we will keep them. The strengths of our PC's are all over the map with about half decent machines and the other half older stuff. You don't upgrade P2-266's, you replace them. PC's are expensive. The budget drives these things. We'd be VERY cautious to adopt any software that caused half of our pc to be obsolete. Being a tech nut I've love to run out and buy a bunch of new pc's but it's not going to happen. We've laid off about half of our workforce and the IT budget (which was already meager) is frozen. So sure I could show a paper to the COO which describes a slick upgrade path but I'd be a fool to do so. Blowing $10000 (probably more) just to upgrade vfp won't fly.