"jp2msft" <jp2msft@discussions.microsoft.com> wrote in message
news:B53C255C-76F7-471A-B320-F5A7F4647167@microsoft.com...
>A Microsoft Access database sounds perfect for what you are wanting to do.
> This database was used for years until Microsoft realized they could make
> more money with SQL Server, then suddenly running an Access database
> became
> taboo.
>
> Access databases are only good for one person accessing the data at a
> time,
> and they have a 2GB size limit.
>
> Another option would be to use an XML file to store your info. The good
> thing about using an XML file is that if you decided to expand to
> including
> your data on a server, there would not be anything to do but redirect the
> path to the file.
>
> Also, modern Microsoft programs in Visual Studio have a lot more examples
> on
> how to code an XML dataset than they do on how to code an Access dataset.
>
> Access is still good, but it has been Eight Balled for some reason.
>
> "Debbie.Croft@nospamforme.com" wrote:
>
>> I'm writing an application that needs to store data locally (in C#). This
>> will be deployed on end-user machines (XP, Vista and 2003 Server). I want
>> to
>> store the data in a database. The volume of data is not huge (about 1 to
>> 5
>> megs).
>>
>> My question is what database to I use? I can only assume the users will
>> have
>> standard installs of the operating system (fully packaged). There is no
>> SQL
>> Server or anything special on them. I need to create the database - not
>> just
>> use it.
>>
>> Do I have to install a database engine, or is there one shipped as part
>> of
>> the OS. If I have to install one, what is recommended (e.g. free, least
>> invasive and most documented)?
>>
>> I used to used DBISAM and Delphi, which was great as it compiled straight
>> into the exe, but I've never done any local database work under .NET -
>> only
>> connecting to remote SQL databases.
>>
>> Any advice would be appreciated.
>>
>>