Discussion Locked

is there any db for me other than access

0 helpful
20 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Dear Friends
I am facing a problem in my project hope you can solve it.

I have developed a project which is for win9X clients and I have takent he access as my back end. but to make the clients access the database the server system whichis a ordinary win9X system is getting very slow in LAN. The same software I have used win SQL as backend and it is able to do the work very well.

Iam able to see that to make the clients access the database server that system should be mapped by the clients, so totally 11 system are accesssing the database server (win 9X system) so it is getting busy and is very slow in LAN. But this is not in SQL which is using NT as base.

You can ask me to go for NT but my clients are or very low budjet people most of them can pay for just 9X system and cannot got for an NT version.

Please tell me is there any other way other than access by which i can use as backend and the LAN also wont be in busy.

If you have any quries you can directly mail to this mail id shivanaidu@rediffmail.com

20 replies

by donq

You didn'd mention Record Counts and or application functionality (much CPU processing etc.) With 9 users Access should work FINE unless the Tables are huge! It sounds as though your low-budget client may remain a slow LAN client without a little investing. I ran into a similar problem years ago where the client attempted to use a telephone modem to transfer record input.

SQL Server, Oracle, DB2, Informix, etc. are all options if your ".mdb" file size is your problem (bigger than 2 or 3 meg after compaction).

by donq

p.s. Make SURE each PC using the back end has Access loaded locally and is NOT attempting to run Access from the server - very very dumb and slow!

by jennyh

You might also try splitting the Access database. Put the tables on the server and a copy of a 'front end' with the queries, forms and reports on each client. Link the backend database tables to the front end. The load on the LAN will then only be for the query or data source for a form or report and not for the entire database.

Jenny

by kschang

The cost to migrate this to a different DB will likely to be greater than the cost of getting a decent server and go up to client-server structure like MS SQL Server. IMHO of course.

by lo

Hi - My $ .02

If you haven;'t yet done so, do some checking to see if it is the database, number of users, volume of traffic, network load, etc.

Also, I remember 1 case where it worked great for 1 or 2 users but died past that. The problem inthat was the queries were requesting 5-10 times the data needed to actually do the processing. Check your queries to ensure that only data needed is accessed. Esp if you do the query/form on the client and data on the server (which is a good design). If the query is pulling 200-300 (more?) records due to less restrictive select criteria to process 1 or 2 records, then ...

by fofa

I have found in the past, if it is an MSAccess application, about 5 users is the best you can expect, that can be increased to about 8 or 9 if you are using VB as the application language. I don't know if JET 4.0 helps in this regard. I have seen documents that say 10 users using JET is the most you should have. I know someone who had the same problem, and she used Xbase DB on the backend and a VB frontend and could run 15 users with no problems.

by wbeem

How many concurrent sessions do they run? If they can't afford (or won't pay) for SQL Server, consider using the MSDE. It's essentially the same thing as SQL Server, but it's a personal edition. Without knowing more specifics, I don't know if it's applicable for this problem. However, it doesn't have to pass the entire database across the LAN to each client, like Access. Instead, you only need pass the answers to the queries.

--William

by limbo

kschang's answer is 100% correct, provided the server itself is the bottleneck.

But if the true bottleneck lies in the LAN itself (packet collisions, poor topology etc.) Then address this first.

A good DBA Administrator recognises the need tocontinuously monitor network performance anyway.

If you can guarantee that the Server is not the bottleneck, or that the LAN is not the bottleneck, next target the client.

How efficient is you program? What is the fastest response time you can actually get from any network?

There are Freeware and Shareware tools that do this.

OK now assuming you satisfy these conditions, consider upgrading to a RDBMS like MS SQL Server, oh and don't forget to make your database efficent - easier said than done.

If you attempt take the final solution without knowing the true extent of the problem, you may face unbearable costs.

by pjbates

I'd second the MySQL suggestion.
It may require some reworking of the application, but if you have stuck to either plain SQL / ODBC it shouldn't be too hard.
The database is free, and it will run on any win32 platform inc win95 (as well as all unix based systems).
You'll be doing yourself and your clients a favour moving to a more robust DB solution. Access is good for a single user, and thats about it.

This discussion is closed to new replies.