|
|
I am developing a software package which needs a database backend. In the past I have used Access or SQL Server as the backend for my applications. However, for the application I am building I do not want to require my users to have to have the backend database (like access) in order to use the software. Are there any thoughts on what I can use to manage table relationships without forcing my users to purchase something like access?
|
|
|
|
if your database application is small to medium and limited to 10 simultaneous user access to database, you consider using MSDE database. MSDE is sql server database engine (avaliable with 97 and 2000 versions) and it's FREE.
For more info and to download MSDE
http://www.microsoft.com/sql/msde/downloads/default.asp
|
|
|
|
MSDE2000 is good, as previously suggested. I also want to point out that Access does not require any backend for your users--just the access file.
Well, technically, your users must have Access drivers installed, but you won't find a Windows PC that does not. All you need on the user's computer (or your web server for web applications) is the Access file. (you .mdb file) You do not need Access installed on the server or user's computer.
|
|
|
|
|
|
I agree with your point. I thought used asked some database with RDBMS features like object relationships and indexes..
I hope access driver is preinstalled in most windows machines and end user doesn't need to install (or buy) access in client's machine..
|
|
|
|
Shan, I see your point...troyvw says "Are there any thoughts on what I can use to manage table relationships without forcing my users to purchase something like access?" This sentence has a logic problem because Access doesn't manage table relationships. So you could interpret that troyvw is looking for an RDBMS specific solution. I interpreted it that troyvw was just looking for a way to have a "database" that did not require installing a database engine on client computers and probably one that does not require licensing. MSDE2000 does not require licensing, and it is very powerful as long as you don't need more than 10 simultaneous users (as you point out, Shan). But, it does require installation on the client computer--it is a "database backend". I think troyvw mistakenly thought an Access mdb file requires the Access backend to use it. My point was simply that you can have an application using an Access mdb file as a database without Access installed on the computer. Many ASP websites use Access as the database and Access is usually not installed on the webserver. PLUS it does not require any licensing.
The ODBC drivers for Access are definitely standard parts of all Windows Operating Systems. Also, no licensing is required to distribute an access file (.mdb) and use it on as many machines as you want. The Access program provides both a development environment and a user front-end to the database file. Access requires licensing, but the database file itself does not.
This is why Access files are so popular as databases for small ASP Web applications. The developer uses Access on his/her workstation to develop the database. Then he/she just copies the mdb file to their webserver and their application uses it via ODBC methods in the code. NO LICENSING is required, and nothing must be installed on the server except the ODBC drivers which are already there by default when you install Windows on the server. On the other hand, to use SQL Server in a web environment is quite expensive. Last I remember it was $5000 per processor for SQL Server Standard. PLUS you have to install and configure it. Of course, SQL Server is faster, more scalable, feature rich, provides programming layers of its own, yada, yada, yada (SQL Server is what I use, and I love it.)
For very simple applications that only need a small amount of data stored, I'm looking into using simple XML files. With ADO.NET, you can use an XML file as a datasource in almost the same way you work with Access or SQL Server or Oracle. I'm working on an online document library application where the program builds the library automatically by starting in a root folder and reading through the branches to build an XML catalog. The admin tool would allow you to give each folder and file a title and description, etc. The browsing tool would allow sorting, searching, and viewing of all documents in the library. New documents could be added via the admin tool, or just dropped somewhere in the folder structure--the application would find it. Now I'm rambling....my point is, I'm going to use XML as the datastore for this project.
Anyone have sample XML as a datasource code projects to share? Would love to see it!
|
|
|
|
|
|
|
|
|
// |
troyvw
Shan
