Upgrading with halcust and halpatch
Paul Timms
1-17-18
When upgrading using MyStandard, what is the correct procedure to apply a new halcust and halpatch?


The upgrade option lets you apply a halcust or halpatch folder, which I'm told should be a zip file. It's not clear how you upload both a halcust and a halpatch since you can only choose one.

When you select to run the upgrade, with a halcust.zip uploaded, it creates the text backup, then moves the existing halcust and halpatch, along with the HDB and other system files, into an oldver folder. It then applies the new system files and imports the backup. However, it does not apply the new halcust and/or halpatch, therefore the import can be a waste of time if there are changes to datadef. You then have to manually copy the halcust and halpatch folders to the server, assuming you have access, move the LCSUPDATE.TXT into the Backup folder, rename it to TBxxxxxx.TXT so that MyStandard can see it, and then use MyStandard to restore that backup.

The above process is OK for smaller systems, but not viable for larger systems as the export/import simply takes too long. The upgrade process should be as smooth as possible.
Leave Comment
You can subscribe to notifications for this post by selecting the 'star' icon on the top right corner of the post.
Latest Posts
Bror-Erik Kotiranta
Clients have their own cache, and then the server has the shared cache, if you want it kind of black and white. Presense should be there as far as i know...
10:55 7 July 2025
Yavuz Yigiterhan
Hello Paul, That is something only HansaWorld can do. But that would help to understand is that causing the problem and - if so - we fix the issue. Additional information is appreciated. Yavuz...
10:45 7 July 2025