Bad idea for so so many reasons.
First, not at all scalable as a DB. Need more horsepower for an Access
DB? Buy a more powerful machine. Need more power for SQL Server?
Cluster it.
Second, horrible for design & maintenance. Need to make a change to an
Access database? You've got to take it offline...becomes even mroe of a
pain if you don't have local access to the .mdb file.
Go with SQL Server or Oracle. If money is an issue, see if MSDE can
work for you, or try MySQL. Leave Access for the secretaries and the
guys who run fantasy football leagues.
Just my $.02
Pete
David Brown wrote:
> Is this good idea? If not; is there an article I can referance for my managment?
>
>
>
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
- MS Access as a backend database David Brown
- RE: MS Access as a backend database Philip Arnold
- RE: MS Access as a backend database Tony Weeg
- Re: MS Access as a backend data... Eric Dawson
- CF (BD) on CD with DB Succ... Dick Applebaum
- Re: CF (BD) on CD with... Spectrum Web
- RE: CF (BD) on CD with... Yves Arsenault
- RE: CF (BD) on CD with... Tom Kitta
- Re: CF (BD) on CD with... Dick Applebaum
- Re: CF (BD) on CD with... Dick Applebaum
- Re: MS Access as a backend database Pete Ruckelshaus - CFList
- Re: MS Access as a backend database Jochem van Dieten
- Re: MS Access as a backend database techmike
- RE: DateDiff to determine number of weekdays pas... Pascal Peters
- Re: DateDiff to determine number of weekday... Shannon Carr