A little more information. In order to use a database
developed in Access using a .mdb file (Jet db engine)
would require you to upgrade to SQL Server, probably using
the upgrade wizard. Then you would need to correct any
code which is incompatible with the new configuration.
For instance, DAO can't be used on a .ADP file connected
to a SQL Server, then you would need to rework the queries
to stored procedures using T-SQL to get any real advantage
over Access. If you have a simple database this could be
a simple upgrade. If you have a complex database this
could be a complex upgrade (read nightmarish). You get
many more capabilities with SQL Server but they are NOT
free. Many times the best choice is not to upgrade.
Access does a great job when it is sized properly.
Some tasks:
Rewrite VBA code to be compabible, DAO to (ADODB and ADOX),
Create logins, usernames, roles, groups for secure systems,
Modify stored procedures for security as required,
Rewrite VBA functions into T-SQL functions,
Load and configure MSDE for development,
Learn SQL Server administration for development,
Learn DTS for data transformation,
Learn how to use the Query Analyzer, Profiler, and
Enterprise Manager
You need to make an informed decision if you are upgrading
legacy applications. It's frequently easier to start from
scratch. I'm glad I made the decision to upgrade (some of
my applications) and learn all the technologies required
but I still have many apps NOT upgraded for a good reason.
Steve King
