Converting Access 97 to 2003Adam CoganDatabase Architectssw.com.au
About AdamChief Architect for www.ssw.com.au - experience with:internal corporate development andgeneric off-the-shelf databasesClients: Enterasys Networks, Cisco, MicrosoftRun Teams of DevelopersPresident .NET User Group, SydneySpeaker for Microsoft Roadshows, Dev Conn, VSLiveMicrosoft Regional Director, AustraliaEmail: AdamCogan@ssw.com.au
ToFrom
OverviewAccess 97 toAccess 2003AccesstoSQL ServerAccesstoReportingServicesAccesstoWindowsForms .NET 1234
AgendaWhy Upgrade?Current ProblemsDemo: Converting Northwind 97 to 2003
Why Upgrade?PivotTable and PivotChartSmart tagsError checking in forms and reportsBetter help system
AssumptionsDatabase in Access 97Familiar with VBA/DAO
Upgrading IssuesDatabase in an uncompiled stateLinked TablesToo many code or class modulesMDE files cannot be convertedAdditional referencesSecured databaseUser-level securityDatabase passwordReplicated database
Current Problems1. Database in an uncompiled stateCause: The IsCompiled property is falseResolution: Compile the database with the old version of Access before trying to convert. Fix any compile errors.
Current Problems2. 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 Problems3. Too many code or class modulesCause: Greater than 1000 code modulesResolution: Combine or eliminate modules until the number is less than 1000
Current Problems4. MDE files cannot be convertedCause: Database is an MDE fileResolution: Obtain the MDB source file, convert and recompile
Current Problems5. 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 Problems6a. Secured database database passwordCause: An end-user has secured a database with login securityResolution: The person converting the database must have the necessary permissions
Current Problems6b. Secured database user-level securityCause: A workgroup administrator has secured the databaseResolution: The person converting the database must join the active workgroup
Current Problems7. Replicated databaseCause: Database is a member of a replica setResolution: Synchronise replica set members before conversion
Tidying up your databaseTidying up your database before upgradingForm performanceUnused database objectsMissing error-handling codeFMS Total Access AnalyzerAnalyses database for problems
SummaryCurrent problemsDatabase in an uncompiled stateLinked tablesToo many code or class modulesMDE files cannot be convertedAdditional referencesSecured databaseReplicated databaseTidying up your database before upgradingFMS Total Access Analyzer
For More Informationwww.ssw.com.au/ssw/Events/2004AccessToSQLServerAndNET/Resources.aspxwww.fmsinc.com
2 things
AdamCogan@ssw.com.au
Do the migration demo now. The next slides are for directly after
