>>Nice point -- 16 bit apps. But as VFP grows more complex will you be able to support both platforms -- and have the time?
>
>At the risk of being really assulted, I don't think there will much of a market for 16 bit apps in the "near" future. Most companies that I have talked to (many of them, however, are upstart companies, with no legacy systems) are thinking "NT"....
>
>Fire away Boys! (s)
>
>Scot.

Boys? Hey, hey, hey...you were just trying to get me to check in on this one, weren't you?

Sorry, I was out yesterday. I, for one, tend to come down on Lucien's side on these arguments. I'm in Atlanta, not exactly a backwater, and you can't beleive how much demand there is for maintaining/updating even 2.5 DOS applications. As I've said before, I'm on a government contract now, and when I asked the network admin folks (alias the Network Nazis) when I could expect the division to upgrade to Win95, the answer was December. Of 1997. I also have twelve public health sites out there running the data collection end of this app, and you can't imagine what kind of dog's breakfast of hardware there is in the field (hey, I've got sites in Arkansas, you know what I mean?)

Yes, it gripes me when I have to drop down into 2.6 (or 2.5DOS) to do something, and I spend half a day reinventing the wheel to arrive at a control that would be automatic in 3.0, but that's why I make the big bucks, right?

Fact is, it will be years before I can depend on clients having 32-bit systems. The management around here decided last spring that everything was going to go on Powerbuilder, and I spent six excruciating days in PB class. Then they remembered that we'd have to upgrade about a billion computers on a government budget, and they went gently into that good night.