Alternative to using Access as database backend?

[softwareguy74]

Hi,

I'm interested researching possible alternatives to using Access as
a database backend for my VB6 application.

There are a few reason for this but I will not go into them here..

I have noticed that most database type applications that I have used do
not seem to have a .mdb file associated with it. So it seems that there are other alternatives to Access out there but I'm just not aware of them..

It will be small to mid size desktop operation in a single user environment so I would obviously not need SQL server.. Here's what I'm looking for:

- light weight (doesn't take too much space)
- easy to program
- something that will let me perform SQL queries against
- something that will not let the end user open up the data file
and be able to read it
- something that would not require me to purchase another program (maybe something that could be made with a text editor?)

I know I could use a text based database, but it seems to be very limited..

Also, I would prefer to use a format which ADO could interface with but it's not absolutely necessary..

Any help or guidance or resources on alternatives to Access would be appreciated..

Dan

[Shafee]

I have also been looking for another alternative to Access. Can you pls let me know if you come up with something?

[Shafee]

Hi Hudg,

I have followed installation instruction in MSDN, but MSDE does not work. I get the following message:

Connection failed:
SQLState: '01000'
SQL Server Error: 161
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen[CreateFile()]
Connection failed:
SQLState: '08001'
SQL Server Error: 161
[Microsoft][ODBC SQL Server Driver]Client unable to establish connection

I am using Win98.
When I try to connect, I am asked to enter a username and password. Is there a way to set up a username and password?

[hudg]

About the Username, with MSDE it follows the same rules that SQL would. If your app is designed for a Network, then you could user you Lan Account, or you can create account. Either way you can input the username through ODBC or code.

here are some things to check concering the connection error:
Concerning your connection error, make sure the service is started, by default it is not started after installing it.

In addition what network libary did you use? Name Pipes or TCP/IP?

Make sure you MDAC 2.5, it offers a better interface for SQL Connections. You can test your connectivty, great for troubleshooting.

If you don't the use a import utility to import a database, then you must connect to the master database.

Try using Visual Data Manager to connect to the MSDE

[Clunietp]

If you guys are looking for a text based alternative, you can persist (save) ADO recordsets to a file. You can then open the file, sort it, manipulate it, etc. You don't need any external apps, and it won't cost anything extra.

the downsides to this approach:
-each table would be a separate file
-no referencial integrity checking (unless you code it yourself)
-no indexes (unless you code them in, once again)
-the user can open up the file and read it
-(probably a bunch more as well).....

There are also other database formats out there, but ADO does not work well with them (in most cases, you can only get read only access to databases like DBase, Paradox, etc)

You are usually better off using MS Access databases, as they work great with ADO and cost nothing to distribute. You also get the benefits of a DBMS to manage your data, and if/when you need to upgrade to SQL Server/Oracle, it is easy to import your data and you won't have to make many code changes

HTH

Tom