My experience with multi-tier architecture using only VB does not yet extend to systems beyond 2 or 3 dozen concurrent users. And we feel like pioneers in this technology as it is hrd to find others. However, with my 40 years in application design and programming and my 3 years in this technology, this all has the feel of really good stuff. Also, Microsoft say they have "bet the company" on it.<br>
<br>
I recommend strongly that you get a copy of "Application Specification for Microsoft Windows 2000 for distributed applications" at
<br>
To your questions: We do not use application flow modeling. We do use an Erwin product in designing database schema.<br>
The only limitation we have has been self imposed. We did not use MTS (Microsoft Transaction Server) for our 2nd tier and this may have some limitation with scalability. However, with Win2000 and COM+ we will incorporate MTS functionality for its object pooling.<br>
<br>
We are pleased with our decision to use only one language. We made the decision simply to conserve training and startup resources when new languages are adopted. VB itself was new to us. We decided to use outside programmers for C++ if we needed for execution efficiency. So far this has not been needed. Our apps are not now web enabled. We anticipate the possibility of the need for Java when we do, however VB may work there also. It's a matter of whether your users need to use browsers. Our apps are designed to be used in house, so we have a choice.<br>
<br>
As to using our approach for your company, our approach is Microsoft's approach. Also, we have developed code generators which create about 80% of the lines of VB code for both the UI tier and the 2nd tier. We gain much code reuse in UI and 2nd tiers. Our 3rd tier is used without change by all or our programs and can connect efficiently with almost all databases, and even that is coded completely in VB. We are very happy with the results, particularly with the universal flexbility for the user to find data with every single data form using full query by forms, and the VB code to do that is inserted by our generators. But we are very small and our work has not been tested in a large network environment. You would be welcome to take a look.<br>
<br>
A key to our use of ADO is the full use of Parameterized Command Objects. Much faster than ODBC and our application programmers do not have to code SQL statements. SQL Server7.0 appears to be the real thing. We have used it for about 4 months with nothing but good results. We do not now work with Informix, but did for several years and expect our stuff to run well with it.<br>
<br>
OOP and multi-tier is great stuff, particularly when we have Windows2000 and COM+. But poorly designed and implemented applications turn into major headaches.<br>
<br>
Good luck with your new technology. Just don't expect the concepts of OOP and multi-tier to come to you easily. It was not all intuitive for me, and that cause a slow learning curve. A good consultant may be hard to find, but may be well worth it.<br>
<br>
John K.