Sebastian,

Other questions to ask. . .

Just because you have MS Back Office does not mean you have to use SQL Server.

1. How many transactions do you expect your tables to grow to?
2. What size network environment do you expect to work in? Any offsite stations? If so, what will your connection medium be? (dialup or broadband)
3. How critical is the security of the data?

Reason that I ask these questions is that depending on the size of your data, the sensitivity to bandwidth demands and the security of your data, you can get a very reliable and speedy application by staying in VFP and not having to use SQL as the backend. I find VFP much more flexible for data management and we have been able to maintain quite acceptable speeds while having joined tables containing several hundred thousand records each. What is your expertise in SQL Server vs. VFP. I would imagine that you want to get this application up somewhat quickly also. One other thing to consider is the user license cost of having multiple client SQL Server connections. No extra charge for client access to VFP database.

HTH,

Bill


>Hi!
>
> I agree that provided information in questioning the issue of choosing between MS SQL and MySQL was poor and I'd like to tell more about my project.
>
>Activity overview:
>First, I'd like to mention that I'm working in insurance domain.The database is supose to have tables with contracts,pays,damages,clients and insurance agents.
>
>Software:
>MS SQL server (because we have BackOffice Small Business)
>VFP (5 or 6)
>
>Network profile:
>TCP/IP with a Primary Domain Controller and Win NT as OS
>
>The process:
>User must input data with their contracts,pays or damages.
>
>
>Expectations:
>speed,reliability
>
>thank you!