>Yes, I know, we're *supposed* to use VFP to create middle tier components in Microsoft's C/S strategy - yes, yes, yes.
>
>But if I also want to plug VFP into the back end of my n-tier designs for smaller to medium-sized business apps, what kind of brick walls should I expect to run into? I'm looking at companies of not more than 100 employees who will be entering/accessing the data (via well designed middle-tier components of course!).
>
>I understand the strategy of implementing local views and moving up to remote views, but I'm just curious about the real-world user loads that actually necessitate that kind of migration. Any experiences with this?
>
>Thanks in advance,
>
>-Bernie

VFP is not client/server, so you have to think about where the queries will run. You're "well designed" middle-tier components will actually execute the queries, which limits scalability. To use views the way you are saying, your middle-tier objects will have to run on the workstation because your application will need access to them. Also, VFP does not participate in MTS transactions. There should be little reason that small to medium size shops can't use SQL Server 7.0. You should read "Designing Component-Based Applications" by Mary Kirtland (MS Press, ISBN 0-7356-0523-8). It is an excellent book that will give you new insight into what you want to do.