Hi
If they don't want DBFs , you can try with Firebird embedded engine, which is a single 1.4MB DLL with all features of the full server but with local database access only. XCopy deployment is possible for both databases and DLL.

I've done something like this and works pretty well (not as fast as with DBFs, of course).
One can have a hard time trying to corrupt a Firebird database :).


>Hi Alex,
>
>>I have a similar situation that works very well. And having the power of VFP, you could "masssage" the data locally very eaily behing the scenes. In one case I had to add support for disconnected notebooks on the field. So it was just a matter of keeping the local sets in DBFs in each notebook...
>
>I do have such a situation as well, and was wondering how it could be addressed *if* they told me to convert from DBFs to SQL Server. Was thinking about MSDE or SQL Express (in the notebooks), but perhaps mantaining the DBFs would be a better choice.