Rommel said:
The main purpose that I want a big data storage such as SQL database is
the
continuation of records from year to year or even from decade to decades.
Coz there is a probability that one access database file will come to its
limit and the records will no longer have a continuity.
That Sir is the main purpose.
Rommel,
Whatever you and your colleagues believe, there is very little actual demand
for a larger capacity Jet or ACE database. They are file-server databases,
file-server has drawbacks for use in "enterprise" environments, and
enterprise environments are the only ones likely to need more capacity than
the 2GB provided by Jet/ACE (or the additional 2GB available with the free
version of SQL Server Express which totals 4GB).
You talk of saving data from decade to decade. Ten years is virtually an
eternity in the computer business... most desktop applications never even
last that long on the market -- it is really remarkable that Access has
lasted from Oct 1992 until now.
Most of the paying work I've done with Access was using Access as a
client-application to server databases, via Open Database Connection (ODBC)
drivers. In every one of those cases, it was neither the size nor
performance that was the determining factor of using a server database
back-end, but the reliability and recoverability provided (re-read Chris
O'C's comments on that subject) by the server DB.
And, you still haven't said how big you think it ought to be. Nor have you
indicated what you'd be willing to pay -- nor whether you'd really want to
get true server database functionality for such a price.
Larry Linson
Microsoft Office Access MVP