>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.
>
>I could do it in Access, which he knows and I hate, or I could do it in VFP, which I know. It's going to be one of these two, as I'm not
>interested in learning another DB at this point.
>
>I guess I'm just looking for thoughts....

Kevin,
You are closing doors to other DBs and limiting to VFP and Access. Anyway let's think of it:
-It is a C# Winforms project
If it is a .Net project then VFP is not a good choice as data source. Access wins here.

Likely your project would grow soon, I would suggest think the future. If you do that then likely both VFP and Access would be phased out from the start. I would surely look into one that does have Entity Framework providers.

SQL Server, SQLite, Oracle, Firebird, ... are all easy to install and have EF support today (and express/free options). SQL Server CE database is a single file and have a small footprint. SQLite likewise needs to copy a single DLL. VFP and Access, OTOH both need OLEDB (and unlikely ODBC) drivers be installed before you can use from .Net (and even after they are installed they are unlikely to be the choice).

It is your decision anyway:)

PS: If you go to VFP/Access route strictly then choose Access keeping in mind that otherwise you would limit yourself to 32 bits.

Cetin