All the problems you mention are not normal.

a. See http://www.craigberntson.com/Articles/kb005.htm on my web site for ideas.

b. Can you elaborate on that?

c. Difficult to say what's causing the child/master problem, but most likely it's due to application design, not VFP itself.

>Hi,
>
>We have decided to change VFP native database to SQL server database for following reasons.
>
>a. VFP database (index) gets currputed. (Is there any virus which is doing so?). Duplicate records getting saved in presence of PrimaryKey!
>
>b. Non consistency in data saving.
>
>c. Poor handling of transaction. Data is getting saved in child and not in master. Record locking issue in Multiuser environment.
>
>
>1. What are the issues involved?
>
>2. What is the best architacture available (for VFP + SQL)
>
>3. Any Samples?
>
>
>TIA
>
>Diptesh