Newbie Question: Access vs SQL Server
On Tue, 30 Mar 1999 13:25:11 -0800, "Follo, Thomas
Quote:
>Would appreciate any insight or help on whether to use an Access
>database or SQL Server (or other ODBC...) for a client server project.
>Just touching datbases in VB6 after coming from a VBTelephony project
>using VB3 and flat files, (lots of flat files...).
>Anyways, the project has 3-5 users max in the longterm and we would use
>the database to store Administrative data on users etc and call records
>in our app. Although the call records tables might be small to start
>off, I estimate that everyday they will be 200 records added to the
>table and a user might want to view and sort throught the various
>records. Our current plan is to have one server handle all the
>information access (to the Acess database) and send the records and
>other information across the network to the users via a web browser or a
>simple client app (winsock talking to server)
>Any advice or pitfalls to avoid? Very new to databases and client server
>so any comments would be greatly appreciated. I heard that Office 2000
>is using a new database format for Access 2000 and not sure if Access
>would still work well with VB 6 in the future?
>Thanks in advance,
>Tom Follo
>My $.02 here. Access is not a true client-server database and hasn't
nearly the stability and strength of SQL Server. 3-5 users is ok for
Access, and 60,000 records per year for a year or two would be ok also
but eventually it'll get wiggy. Access is a DESKTOP database
application, and a darned good one too, but it pains me to see what
oughta be legitimate client server systems crippled by using it.
Don't worry about it being compatable with VB in the years to come, it
will be, but don't expend your time/money on a system using Access
when you can be using SQL Server.
Good luck. Happy coding.
Tom
