Support Articles Explaining Various Upsizing Issues
Problems with Data and Database Structure
-
Using New SQL Server 2008 Data Types
This article discusses the advantages and limitations of choosing to map Access data structures
to use new SQL Server 2008 data types such as DATE, and provides instructions on the changes you need
to make in MUST to perform a mapping to a new data type.
-
Upsizing and SQL Server Collation Codes
Access applications are not case-sensitive. However, if you upsize to a SQL Server which has been configured as case
sensitive you may need to take a deeper look at this issue, this article discusses when this can occur
and some strategies for dealing with the problem.
-
SQL Azure and Microsoft Access
Please note the date on this article, as features change in Azure this article will be updated. This
article looks at how you can link Access Databases on the desktop into SQL Azure.
General Issues in Application Development
-
Getting started with SQL Server Security
This is an introduction to SQL Server security, providing an
overview of windows authentication, SQL Server logins, database roles and schemas.
All an Access Developer needs to get started.
-
View updateability affects with multiple base tables
Sometimes you can create a query in Access, but when you convert it to
to a view in SQL Server you get errors telling you that the view can not be updated
because it affects multiple base tables, in this article we explain this problem
and show you a work-around.
-
Access application changes after upsizing to SQL Server: Part I code changes
This article looks at basic code changes that often have to be applied to an Access
application once the data has been upsized to SQL Server, code examples of what to do about
dbSeeChanges, and the impact on code of having autonumbers and defaults only available
after a record has been saved are discussed.
-
SQL Express backup & maintenance
SQL Express does not have any provision for performing regular maintenance on a SQL Server database
or backing up the database, this article explains how to get started creating your own routines to do this.
-
Generating default values for fields in a form
In Access applications you will be used to having the default values for fields displayed when
a new record is entered, but when connected to SQL Server no defaults will be displayed, these are
only assigned after saving the record. This article discusses systematic code to locate and
display default values from the SQL Server table when the new record is first displayed to a user.
Converting and Translating SQL
-
Solving complex query calculations using nested queries
In Access queries, calculated fields can refer to other calculated fields. However, in SQL Server the calculation
needs to be restated. This technique shows how to avaoid the problem using nested queries which allow a
calculated field to refer to another calculated field by name without restating the calculation.
-
Hands-On SQL server - Translating SQL data between Microsoft® Access™ and SQL Server - Parts I and II
Published in the December 2007/February 2008 in the Visual Studio Journal (www.vsj.co.uk),
these two articles discusses in depth translating SQL.
The first article includes a discussion of form and screen parameters, date calculations and arithmetic.
The second article discusses Insert, Update and Delete,
date comparisions, boolean comparisons, aggregates, domain functions and subqueries and summary queries.
Multi-Tenanted Design