missimaths (AT) hotmail (DOT) com wrote:
Quote:
I am currently using Access but will soon need to change to something
that can handle larger amounts of data. SQL Server is an option but
(and please excuse my ignorance here) is that not just used to store
the data? I would need to be able to manipulate most of the data at
once and would using an Access front end not be the equivilant of just
using an Access back end?...i.e would the "manipulation" run in access
or SQL Server?
Also I have a large amount of code (VBA) behind my access, would this
need to be modified if SQL Server were to be used?
If the only problem is that you are nearing the 2GB limit for an .mdb
|
file then moving the data to an SQL Server database and linking the
tables to Access will solve it.
If the "larger amounts of data" means more users and/or more
transactions you will still get the benefits of a more robust
database. With linked tables you are using Access as an application
program and the underlying SQL statements are sent to the "real"
database for execution.
Of course, if the application is the bottleneck then the change won't
help. If you are using Access to read the Bank of America's overnight
batch transactions and apply them to a database then a rewrite is
required.
Finally, I should add that you are not restricted to SQL Server. You
can use any database with an ODBC driver which means almost any
database you have heard of and many you haven't. I have a list of free
ones (including Microsoft's) at <http://database.profectus.com.au>.
Before you choose make sure the identifiers you have used in Access
are valid identifiers in the new one.