Hi Chris, George

>>While n-tier certainly has its place, there will still be solutions requiring a single tier.
>
>Don't tell me, I mainly write single-tier applications without SQL-Server backend. But that's not the way Microsoft seems to see the future of software. Unfortunately.

Same here. Bottom line is that there is a huge market for small to medium-sized app developement where n-tier, SQL-Server, and Web access are not needed and not even desirable in terms of requirements.

While I designed my framework to handle back-end servers (and I happen to love SQL-Server 7.0), I have yet be able to justify and recommend it's use based on the requirements of my current contracts.

On the other hand, I have seen alot of job postings for VB/SQL-Server work. The funny thing is that I see the same companies post these same openings for months and some even from last year. This tells me that they are not having much success with VB/SQL-Server developers/developement. At one time, I was thinking of starting a company called FVBS Inc (Failed-VB-Solutions, Inc), but I figured it would piss-off Microsoft and would not help the Fox community.

>>Lastly, while SP3 does bring new potential for the middle tier, I wouldn't say it does so exclusively. The Datasession object can be utilized effectively in a single tier solution.
>
>Sure, especially because it doesn't have the bugs of a formset and the limitations of a form when you want to create a private datasession. But even in the description Microsoft said that the new session class is intended to be used in COM servers to create non-visual objects with a private datasession.

I just finished redesigning my bizobject framework classes utilizing the new Session class. While it can be used as a COM server, I haven't yet implimented ADO or any type of record set retrieval mechanism - waiting to see what's on the horizon for a VFP OLE DB provider. Until then, it works great for 1-2-tier stuff.