I am planning to develop a desktop application with backend database.

Please suggest me which database i can use. I need to proved a setup of application for each client.

1) MS Access
2) Sybase Anywhere
3) MySql - can I include Mysql database in Setup.exe.


Please suggest me if there is any other database which i can use.


Thank you

BGARA

As a DB designer for a few years one of the first questions I ask is, who will be accessing the data, ill they have the necessary application instaled ad many other questions.

For example, if I was designing something like that and the workforce was in an office I might be inclined to useMS Access because it's localised and evryone can acces the data (providing they have MS Access installed on their terminal.

However, if there's even the slightest hint that the application may be used by a mobile workforce, that 3rd party clients may be accessing the data or that their requirements will grow I'd move to open source and then as their requirements grow the application can grow with them.

In short...

For a quick easy solution that's not going to cost them much: MS Access for everything else: PHP & MySQL.

Hope that helps...

depending on what you are going to use as an installer.
But you should be able to spawn the setup of mysql along with your application. MSDE or SQL Express can also be installed with your app

For Access, you could could add the mdb files as an related file and have them put on to the target machines HD.

Sqlite !

It's a SQL engine programemd in C, that use a local file as container. It don't use any network connections, and give a wide range of connectors (c, c++, java, php, python...) to integrate it in your applications.
PHP5 support it natively, it's often used in portable device, and I even believe that firefox3 will use it to store bookmarks and history

http://www.sqlite.org

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file. The database file format is cross-platform - you can freely copy a database between 32-bit and 64-bit systems or between big-endian and little-endian architectures. These features make SQLite a popular choice as an Application File Format. Think of SQLite not as a replacement for Oracle but as a replacement for fopen()

SQLite is a compact library. With all features enabled, the library size can be less than 250KiB, depending on compiler optimization settings. (Some compiler optimizations such as agressive function inlining and loop unrolling can cause the object code to be much larger.) If optional features are omitted, the size of the SQLite library can be reduced below 180KiB. SQLite can also be made to run in minimal stack space (16KiB) and very little heap (100KiB), making SQLite a popular database engine choice on memory constrained gadgets such as cellphones, PDAs, and MP3 players. There is a tradeoff between memory usage and speed. SQLite generally runs faster the more memory you give it. Nevertheless, performance is usually quite good even in low-memory environments.

...

SQLite responds gracefully to memory allocation failures and disk I/O errors. Transactions are ACID even if interrupted by system crashes or power failures. All of this is verified by the automated tests using special test harnesses which simulate system failures.

As a DB designer for a few years one of the first questions I ask is, who will be accessing the data, ill they have the necessary application instaled ad many other questions.
A) This is a Individual desktop application where i need to provide a setup with install every thing in thier desktop.

The second thing I heard is MSAccess database file corrupted so often. I that correct.

The only time I have had problems with corrupt Access dbs is when they have been allowed to grow over the 4Gb limit and the data get truncated.

Other than that they are pretty robust. I have an unattended datalogging application written in VB running in several locations with stand alone Access .mde files, the system creates new datafiles on a monthly basis, does automatic backups and configuration restores should any corruption be detected.
There is 2 or 3 years data stored on the machines and no one has run up having a major flap as yet (touch wood)