>>>>>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....
>>>>
>>>>Why won't SQL be an easy option ? backup, restore at home. SQL Express is free.
>>>
>>>We're talking about someone who has never even HEARD of Sql. For us it;s a no brainer. To some people, an install wizard would panic them.
>>>
>>>He's already got to install my app. The database should be transparent.
>>
>>He should not have to know anything about SQL.
>>
>>Your app can control all SQL functions.
>
>He would have to install it. And how would he take his data home? With a file based DB he can just copy it.
And with a SQL db he can backup to the thumbdrive and take it home.
As has been said, you can build the backup and restore right into your app.
These are not serious obstacles and are far outweighed by the advantages of using SQL with a .NET app vs a kludge with OLEDB/ODBC against dbfs.
Charles Hankey
Though a good deal is too strange to be believed, nothing is too strange to have happened.
- Thomas Hardy
Half the harm that is done in this world is due to people who want to feel important. They don't mean to do harm-- but the harm does not interest them. Or they do not see it, or they justify it because they are absorbed in the endless struggle to think well of themselves.
-- T. S. Eliot
Democracy is two wolves and a sheep voting on what to have for lunch.
Liberty is a well-armed sheep contesting the vote.
- Ben Franklin
Pardon him, Theodotus. He is a barbarian, and thinks that the customs of his tribe and island are the laws of nature.
