I actually raised the same question to one my local colleague whom I assume technically knowleable in VFP/VB/SQL Server combination. His answer is that use VFP/SQL Server if it is a 2-tier C/S which we do. Use VB/SQL Server if is n-tier C/S. He summed it up that VFP seems to have a lot of intermetent errors which are not being addressed by the VFP team which he did not specify it me. We have sooner plans to move on n-tier environment but you already know that I am irritated with VB. When I discussed the issue to the top management and at the same to take a look on Delphi, they give to me the full responsibility of which tool to use. Maybe I am just unfair with VB. If VFP is good enough on an n-tier environment why not? Would you suggest it?
>>When do you use VFP/SQL Server combination and when it is not?
>
>A bit of an open ended question... I don't think there is one right answer..
>However, there are a few guidelines to consider:
>
>If you:
>
>- Need integrated security
>- Need replication services
>- Need to scale to large quantities of data that extend beyond VFP's limits
>- Are in a distributed environment
>- Have more than 50 users hitting your system
>
>SQL Server is a good choice...
>
>
>>In the same way, apply the same question to VB/SQL Server (specific to John as >I assume that Walter don't use VB.)
>
>Check out my previous posts on this very topic...
JESS S. BANAGA
Project Leader - SDD division
...shifting from VFP to C#.Net
CHARISMA simply means: "Be more concerned about making others feel good about themselves than you are in making them feel good about you."