This can get really long - I'll just give you a couple of my impressions from the conversions I have done..

>Hi everybody,
>
>I'm interested in the experience of the people who had large multi-user (~60 - 100) project converted from VFP Database to SQL Server database. Can you please tell me what route you take, how much of re-write it was, how long does the project took.

I use SPT exclusively - it requires a lot more changes in most existing systems, but in the end performance and reliability justify losing DBCs and DBFs completely.

>
>Few more specific questions.
>
>For PK/FK we're using "pseudo" GUIDs (just alphanumerical). Should we use uniqueidentifier field in SQL Server for them?
>How can we get new ID after insertion using this type of field?

I use SQL Server autoincrementing integers. Foolproof.

>
>Also currently each form has BO which are based on one table (using local view). In the Save method there are VFP transactions used and record saved first in the parent, then in children. If anything fails, transactions are rollbacked.
>
>IMO it would make sense to use one SP in SQL Server for all of this process. But how exactly does it work and how can we pass parameters?


There are more ways to do this than opinions. I'd prefer to use SQL SPs to handle business rules and let SQL RI based on FKs handle integrity.

>
>Thanks a lot in advance for your input.