>>>>>I'm working on a small MS Access to C# WinForms conversion project. I have to decide which database to use. The client will most likely want to take the data home, so SQL will not be an easy option.
>>>>
>>>>SQL is as easy an option as Access.
>>>
>>>How do you figure? SQL has to be installed. I can just copy the VFP tables to the Data folder and access it using .Net's oleDb driver.
>>
>>Or you could put it all on sticky notes and paste it on the monitor <bg>
>>
>>SQL Express takes a few minutes to install and is a real database. Attaching and detaching databases is really quite simple. Give it a try. If you're moving from Access to C# I don't see where VFP should even play a role.
>
>I see any form of SQL as more overhead than necessary. Getting a DB on this guy's PC is as easy a copy & paste with VFP. No setup wizard. No multiple forms of connection strings with a VFP DB in a folder called 'Data' under the app folder. With SQL. Seems a whole lot more simple to me.

Kevin there are some issues with VFP and dot net to learn to get around. I use VFP extensively in a windows application but really wish it wasn't. I works great and the speed is great too but the development side for some things is a pita. I mentioned it before but take a look at VistaDB as it is a dot net integrated database. It isn't free though so the best free option is SQL CE.