View
216
Download
0
Category
Preview:
Citation preview
Converting Access 97 to Converting Access 97 to 20032003
Adam CoganDatabase Architectssw.com.au
ToToFromFrom
OverviewOverview
Access 97 Access 97 toto
Access 2003Access 2003
AccessAccesstoto
SQL ServerSQL Server
AccessAccesstoto
ReportingReportingServicesServices
AccessAccesstoto
WindowsWindowsForms .NET Forms .NET
11 22 33 44
AgendaAgenda
• Why Upgrade?• Current Problems• Demo: Converting Northwind 97 to
2003
Why Upgrade?Why Upgrade?
1. PivotTable and PivotChart2. Smart tags3. Error checking in forms and reports4. Better help system
AssumptionsAssumptions
1. Database in Access 972. Familiar with VBA/DAO
Upgrading IssuesUpgrading Issues
1. Database in an uncompiled state2. Linked Tables3. Too many code or class modules4. MDE files cannot be converted5. Additional references6. Secured database
a) User-level securityb) Database password
7. Replicated database
Current ProblemsCurrent 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.
Current ProblemsCurrent Problems
2. Linked TablesResolution: Convert on the local
machine, or use the Linked Table Manager to re-link the tables after the database has been converted
Current ProblemsCurrent Problems
3. Too many code or class modulesCause: Greater than 1000 code
modulesResolution: Combine or eliminate
modules until the number is less than 1000
Current ProblemsCurrent Problems
4. MDE files cannot be convertedCause: Database is an MDE fileResolution: Obtain the MDB source file,
convert and recompile
Current ProblemsCurrent Problems
5. Additional referencesCause: 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.
Current ProblemsCurrent 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
Current ProblemsCurrent 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
Current ProblemsCurrent Problems
7. Replicated databaseCause: Database is a member of a
replica setResolution: Synchronise replica set
members before conversion
Tidying up your databaseTidying 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
SummarySummary• Current problems
1. Database in an uncompiled state2. Linked tables3. Too many code or class modules4. MDE files cannot be converted5. Additional references6. Secured database7. Replicated database
• Tidying up your database before upgrading• FMS Total Access Analyzer
For More Information…For More Information…www.ssw.com.au/ssw/Events/2004AccessToSQLServerAndNET/Resources.aspxwww.fmsinc.com
Recommended