Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Access vs. SQL

Status
Not open for further replies.

storer

Programmer
Mar 27, 2000
41
US
I have a database on Access that is for registration of groups and individuals for events at a year round camp. My office is an hour away from the site where the database will be primarily used. I plan to have the back end on the server, which at this time is Access 97 and front ends on approx. 5 computers, some 97 some 2000. When it's 97 front end to 97 back end, works fine. Having the front end on 2000 slows it down some. I just found out that our computers will be networked (between my office and the one an hour away). Now I will be able to view the database (all data entry will be at the away site. I'll do maintainence, changes, etc...here). My question is will it be really slow ? I don't know much about networking. I've read some about SQL server and wonder if that would be better although we won't have that many users and I don't think we will get hundreds of thousands or millions of records. We also plan to get everyone on 2000 within the next couple of months.

We have been using replication with a different database to handle the distance thing and that works pretty well except when they call and want something new. We usually did a quick fix thing until I could get there. I would like to get away from that.

So what can I do to increase performance over a network?
I have experimented with turning a copy of the front end database into a mde., changed all macros to vba, compiled all modules.

It sounds like the SQL server might be cost prohibitive at this time. If we go that route later, can you change an existing access database back end into SQL server? Is it difficult? I am just now learning code so there would be a learning curve (always on a learning curve) with SQL.

Thanks for your help!

 
SQL will be faster. Yes cost is a factor.
You should have a dedicated NT server for SQL.
So you need 3 things:
1. NT server (Compaq makes a nice one) model ML-350 which retails for ~$1600.00 which is all you need.
2. You need NT Server software for the Compaq too.
3. SQL Server depending on licenses is roughly $1200-$2500.

Also look at an Internet solution instead of a dedicated line between buildings

We have a WEB site that has SQL server on it.
So we can create .ASP pages that work both in house and any where in the world.

It's a slightly different way of thinking but there is no limitation. Anyone with a Internet connection can hook up.
Of course you have everything password protected and behind a firewall.

If you are looking toward the future then WEB based is the way to go.
Also Palm pilots can get on the internet so any people in the company that travel can have a Palm VII and send e-mail, log on the corporate site and get data. You are only limited by your imagination.

We found a discount site for $50.00 a month that has NT servers and ASP, SQL, Front Page 2000. So you can have a SQL database that’s not costing you anything up front because the ISP has it. You are just using the service
We also have a Several SQL servers in house. So I can easily create new tables on the WEB site through and ODBC connection. We are also using DSL as a dedicated connection to the internet.


DougP, MCP
dposton@universal1.com

Ask me how Bar-codes can help you be more productive.
 
Doug,

Thanks for your help! I'll take this to our systems person for discussion on our next step.

storer
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top