Option 2 - Framework --> Existing
This process is destructive of your existing application, so make a copy of your existing application and work from the copy. We will copy new Framework files into your existing project.
- Download the current version of the Framework and extract the files to a new location.
- Make a backup of your current application. Do your work on the copy, not your original.
- Make a backup of your current database before any migration steps.
Merge the Framework in to your existing project
- Using the list of Framework files that match your existing application (see Reference), determine if you made any changes to the Framework that need to be reproduced in the new update. Make a note of all important changes.
- Using the same Framework file list, systematically remove the Framework from your existing application. File by file, remove the Framework.
- Copy the Framework files from your downloaded Framework files to your existing application. If any files already exist, stop and evaluate why the file already exists and make appropriate changes to the Framework.
Recreate any User Defined Functions
- Your existing application may have user defined functions that need to be recreated in the new project.
- The Framework deploys one User Defined Function, named errorout (see here if needed). Be sure to reproduce this in the new project.
- Newer versions of Alpha Anywhere might also have code entries for Node, Xbasic Modules or Classes, etc.
- The database for each version of the Framework is slightly different. You can find the schema for the current version here.
- Each developer has a different method and tools to manage their database, but the basic task is to ensure your live database schema matches the current Framework version.
- Here are some suggested methods:
- Manually compare the current schema to your live database and manually make each modification.
- Use a tool such as Navicat to "compare" your current schema to the current Framework schema, and then update your schema to match.
Publish the new project
- Publish your migrated project for testing. Be sure your initial publication goes to an empty folder rather than over any existing files. DO NOT publish directly to a live location (we don't trust our migration process to be that perfect!)
- Note - sometimes Alpha fails to publish some files or subfolders, check to make sure.
- As above, when publishing, check the box to 'Compile functions in to an AEX file' (at least once during the migration process).
- Be sure to specifically publish the new wt4.aex file.
- It is also good policy to restart your Alpha Application Server after publishing.
- Congratulations, your newly merged project should be ready to use. Once you are sure, take the required steps to replace your live application and database with your new build.
FUNCTION errorout AS C (errormsg AS C = "", severity AS N = 0 )
fldr = "\a5\logs"
logfile = fldr + "\sql_error.log"
if file.exists(fldr) = .f.
vErrorMsg = time("yyyy/MM/dd 0h:0m:0s") + "|" + ErrorMsg + crlf() + replicate("-",10) + crlf()
if severity > 4
' email or SMS code here to send a notice to an Admin