Upgrading MS Access 2003 bespoke databases to later versions

Comments

2 comments

  • Official comment
    Avatar
    FMS Technical Support

    Hello Giles,

    Thank you for considering FMS for your developmental needs.  Based on your description, it sounds like Total Access Analyzer will solve your problem. 

    Total Access Analyzer examines all your database objects to provide extensive documentation, code analysis, object cross-reference, and diagrams with over 390 presentation-quality reports. It detects 300+ types of errors, suggestions, and performance tips, so you can learn and apply Best Practices to fix problems, improve your design, and speed up your Access applications.

     

    To download a free trial of Total Access Analyzer 2003, please go here:

    http://fmsinc.com/sam/myfms/login_dl.asp?url=dt&pid=454883

    To purchase the full version of Total Access Analyzer 2003, please go here:

    http://fmsinc.com/FMSBasket/OrderForm.asp?p=TAAN117

    Thank you,

    Tech Support

     

     

    Comment actions Permalink
  • Avatar
    Rachel Gomez

    To analyze the custom code and identify any deprecated functions or other issues, you can follow these steps:

    Make a backup: Before making any changes or analysis, it's important to create a backup of the Access 2003 database to ensure you can revert back if needed.

    Open the database in a later version of Access: Open the Access 2003 database in the version of Access that you want to migrate to. This will allow you to identify any compatibility issues.

    Compile the code: In the Visual Basic for Applications (VBA) editor, choose Debug -> Compile [Database Name]. This step will highlight any syntax errors or compilation issues in your code.

    Review the References: In the VBA editor, go to Tools -> References. Check if any references are marked as "Missing" or "Unavailable." This could indicate that certain libraries or components used in your code may not be compatible with the newer version of Access.

    Analyze deprecated functions: Manually review your code and identify any deprecated functions or features that are no longer supported in the newer version of Access. Cross-reference the deprecated functions with the official Microsoft documentation or release notes for the specific version of Access you're targeting.

    Test and debug: Make necessary modifications to the code to address any compatibility issues you've identified. Test the database thoroughly to ensure that all functionality is working as expected.

    It's important to note that automated tools specifically designed for analyzing Access database code may not be readily available. However, following the steps outlined above should help you identify and address any compatibility issues during the migration process.

    Regards,

    O365CloudExperts

    0
    Comment actions Permalink

Please sign in to leave a comment.