What are the sorts of changes that I need to make to my Access DB (i.e.
code) when storing data in SQL Server?

If you leave your front-end as an MDB, almost none. Certain queries can be
improved by making them into stored procedures and doing the work on the
server. You can also do Pass-thru queries on the server. The candidates for
this process are any query which runs slowly. You can replace them
one-by-one after the conversion is made.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

"JustinP" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> What are the sorts of changes that I need to make to my Access DB (i.e.
> code) when storing data in SQL Server?
>

"JustinP" <(E-Mail Removed)> wrote:

>What are the sorts of changes that I need to make to my Access DB (i.e.
>code) when storing data in SQL Server?

There can be quite a few changes required. However the first
question to ask is why would you want to change to SQL Server?

Do a search at the Knowledge Base at support.microsoft.com using the
keywords "upsizing" to review the various white papers on upsizing
Access to SQL Server as well as to ensure you have any updates
required.

Also see my Random Thoughts on SQL Server Upsizing from Microsoft
Access Tips page at
http://www.granite.ab.ca/access/sqlserverupsizing.htm

There is a new tool from the SQL Server group.
SQL Server Migration Assistant for Access (SSMA Access)
http://www.microsoft.com/sql/solutio...n/default.mspx

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm