Converting Access 97 to 2003

1
Converting Access 97 to 2003

• Adam Cogan
• Database Architect
• ssw.com.au

2
About Adam

• Chief Architect for www.ssw.com.au - experience
  with
• internal corporate development and
• generic off-the-shelf databases
• Clients Enterasys Networks, Cisco, Microsoft
• Run Teams of Developers
• President .NET User Group, Sydney
• Speaker for Microsoft Roadshows, Dev Conn, VSLive
• Microsoft Regional Director, Australia
• Email AdamCogan_at_ssw.com.au

3
(No Transcript)
4
To
From
5
Overview
1
2
3
4
Access 97 to Access 2003
Access to SQL Server
Access to Reporting Services
Access to Windows Forms .NET
6
Agenda

• Why Upgrade?
• Current Problems
• Demo Converting Northwind 97 to 2003

7
Why Upgrade?

• PivotTable and PivotChart
• Smart tags
• Error checking in forms and reports
• Better help system

8
Assumptions

• Database in Access 97
• Familiar with VBA/DAO

9
Upgrading Issues

• Database in an uncompiled state
• Linked Tables
• Too many code or class modules
• MDE files cannot be converted
• Additional references
• Secured database
• User-level security
• Database password
• Replicated database

10
Current Problems

• 1. Database in an uncompiled state
• Cause The IsCompiled property is false
• Resolution Compile the database with the old
  version of Access before trying to convert. Fix
  any compile errors.

11
Current Problems

• 2. Linked Tables
• Resolution Convert on the local machine, or use
  the Linked Table Manager to re-link the tables
  after the database has been converted

12
Current Problems

• 3. Too many code or class modules
• Cause Greater than 1000 code modules
• Resolution Combine or eliminate modules until
  the number is less than 1000

13
Current Problems

• 4. MDE files cannot be converted
• Cause Database is an MDE file
• Resolution Obtain the MDB source file, convert
  and recompile

14
Current Problems

• 5. Additional references
• Cause Database contains reference/s other than
  STDOLE, DAO, VBA, VBIDE, Access, Office and
  ADODB.
• Resolution The person converting the database
  must be sure to have the same references on the
  machine doing the conversion.

15
Current Problems

• 6a. Secured database database password
• Cause An end-user has secured a database with
  login security
• Resolution The person converting the database
  must have the necessary permissions

16
Current Problems

• 6b. Secured database user-level security
• Cause A workgroup administrator has secured the
  database
• Resolution The person converting the database
  must join the active workgroup

17
Current Problems

• 7. Replicated database
• Cause Database is a member of a replica set
• Resolution Synchronise replica set members
  before conversion

18
Tidying up your database

• Tidying up your database before upgrading
• Form performance
• Unused database objects
• Missing error-handling code
• FMS Total Access Analyzer
• Analyses database for problems

19
Summary

• Current problems
• Database in an uncompiled state
• Linked tables
• Too many code or class modules
• MDE files cannot be converted
• Additional references
• Secured database
• Replicated database
• Tidying up your database before upgrading
• FMS Total Access Analyzer

20
For More Information

• www.ssw.com.au/ssw/Events/2004AccessToSQLServerAnd
  NET/Resources.aspx
• www.fmsinc.com

21
2 things
AdamCogan_at_ssw.com.au
22
Thank You!
23
(No Transcript)