Ok need advice on Database Selection

Currently we use mdb, SQL, Universe, and Pick. Have a requirement to build an app that allows scalability from desktop to server.

Therefore Access no good, really only a desktop db which can be stretched to a server environment.

SQL needs NT to run as server app...no desktop version for Win98 or Wind95

Universe/Pick don't even go there...large scale db...can be run on desktop but needs "Objects" to interface with vb, so out of clients price scale. Actually wouldn't be a bad option if the end users would anti up at the start of the project. Hmmm...can scale from one user on win98 to over 1000 on a server...still price is going to kill that one.

Anybody..........

You might not like this answer but it may be of some use.

Why don't you CROSS PLATFORM it?

One of the beauties of a technology like OLEDB (ADO) is that you can effectively remove the back end of the SQL database and replace it with any other Database server and the whole thing should run providing you change your connection string correctly.

Of course some DB's have their own unique ways of doing things (Called Functional Dependancy) but that can be overcome with some smart coding.

My suggestion would be to use Access on the StandAlone versions because its cheap and for SINGLE user it really isn't that bad.... and use SQL Server on the SERVER versions because it is highly flexible, updatable and scalable (well at least from V7 it is anyway).

All "normal" SQL Queries will work regardless which back end is used (ie SELECT X FROM Y WHERE Z, etc,etc) and you only have to look out when you want to do specifically "funky" things like reading data structures by accessing the system tables in SQL Server (because these dont exist in access).

Then you would simply write your code with Control structures where "Ugly" queries go :

Code:

---

If IsAccess Then
  SQL_String = "Access Happy Query"
Else
  SQL_String = "SQL Server Happy Query"
End If

rstRecordset.Open SQL_String, Connection, .. ,...

---

As you can see the actual functionality doesn't change its just a few nitty gritties of how to read the database.

You may say SQL Server is expensive but I would ask you to find me a client who has a Server of > 50 people that isn't already paying SH#T loads for their software and I can point to a software pirate for you ;)


If you want to use another option that allows BOTH within the same DB you will pay $$$$$ because they didn't build in all that wonderful functionality to allow it to walk out the door cheap.

Hi Jethro

On a side note SQL server 7 can be run on 95 or 98 and is now to slow either on theese platforms.

Hope this helps

Ian

I'm not sure how easily or if at all this will work with VB but MySQL seems te be getting pretty popular for server side work, plus its free. http://www.mysql.com/
When I have some time its one of the things I've been planning to look into, already lost out on one sweet job cause they where looking for MySQL experience.

I thought SQL 7 required a server version installed on NT, with Win95/98 able to connect through client software. Am so confused on this....MS here in oz are no help...where do they employee the turkeys who answer support requests. Clearly ex apple employees.

Have adviced the Client to go with NT server and SQL 7. Notice Karl has started a tutorial on this stuff. Great!!!!!! Normally when l get to a site the SQL databases are setup already. This is the first time they are unleashing me on an entire client/server project.

Will ask around our intranet and see who answers.....