Access to Our Developers Program
Application version 2.02 (build 037) streamlines access by our Developers and Testers to program features currently in development.
Users wishing to assist in the testing and development of the future releases should apply for the issue of a “developers” key. This allows you to access the current development version and test upgrades prior to their public release.
Create a separate Budgets GetReal folder
You should create a totally different Budgets GetReal folder for development. Clearly mark this as “for development”. This will ensure there is no conflict between testing and actual client database files.
This will also allow you to run the two applications concurrently & compare differences on-screen.
Creating a separate test structure is essential for the following reasons:
1. There may be conflict with the Version file downloaded to the database. The development file may have a higher application version & build number. If you then try to revert this to the non-development case there may be problems.
2. There may also be Version problems on reverting to non-developers mode. This is because version files are uniquely time-stamped. Versions can not revert to an earlier timestamp - a security precaution.
3. There is no guarantee that development builds are stable & may not adversely effect your data.
You can only use the development version if you have configured your Database folder for multiple database use. See also Configuring to use multiple databases. Note that the DevelopersKey file overides the operation of your multiUserKey file.
Your developers key
You will be sent a developers key. Save this to a file called DevelopersKey (note without any file extension). Place this file within the Budgets GetReal folder used for testing. DevelopersKey files are digitally signed and must not be altered.
Changes to program launch and basic operation
Launch behavior
The presence of a DevelopersKey changes the launch behavior of Budgets GetReal as follows:
1. The latest development manifest is accessed & downloaded each session. You must have an active internet connection. You work on the latest libraries published at start of your session.
2. The manifest used has reserved name “ApplnManifest-Developers.ich”. It is only used in Development mode. Libraries follow the normal naming conventions - with last build related possibly being automatically updated.
3. If your Developers key is expired then Budgets GetReal will quit. DevelopersKey files are issued for limited periods (see their internal Expires property).
4. If the downloaded Manifest requires a later Application than what you launched, you must quit & reopen with the nominated application. This will automatically launch for you if you choose the “Switch” option.
There may be several application updates before the final release. Keep the downloaded file names eg “BudgetsGetReal_2.01.exe”. This significantly simplifies the update process.
5. The downloaded Manifest may require an update to the database schema. You will be given the option to Update the schema or to Quit.
6. Databases may have been marked as “read-only” in previous operations. If so you will be offered the option to remove this on a sessional basis.
Access to non-public Extensions, Help etc…
Once the main Budgets GetReal window opens, a special Version file is downloaded that matches your Developers key. This allows the testing of later Extensions not publically available, different Help files etc….
The download of this special Version file (and hence access to its content) is not guaranteed. It can be revoked at anytime without notice (& within the expiry of your DevelopersKey). If revoked the publically available Version file will be served.
Certain modes of operation are not respected
Usually there is no database update allowed for AccessKeys (created using the TaxTime extension), databases marked read-only and program access using an Accountants multiUserKey. These constraints are not respected in the Developers version and the database may be updated without notice.
Development files are generally writable and protected against duplicate lockout. Be careful with cancelling AccessKeys (created using the TaxTime extension) - cancelling here may give unpredictable results with ac tual client databases.
Please give us your feedback
Development documentation is, by definition, likely to change. Please advise us of any anomolies or changes that should be made to this document.
