Its now. I have a fix from Clyde.
The problem was in the current view. Clyde said it included some GSAK internal hidden fields which should never be in a view nor be displayed.
The fix, once you get past the error message behaviour is to reset the view. "Tools=>Reset grid to default view"
There will be an automatic fix in the next build.
GSAK 7.7.0.109 update problem
Re: GSAK 7.7.0.109 update problem
Does all this mean I should back something up before I update my gsak? Or is there something I can check to make sure it doesn't go wrong for me? I'm not all that great at fixing things on my computer if they go wrongriblit wrote:Its now. I have a fix from Clyde.
The problem was in the current view. Clyde said it included some GSAK internal hidden fields which should never be in a view nor be displayed.
The fix, once you get past the error message behaviour is to reset the view. "Tools=>Reset grid to default view"
There will be an automatic fix in the next build.
- Facitman
- 1400 or more caches found
- Posts: 463
- Joined: 18 June 04 3:58 pm
- Location: Melbourne
- Contact:
Re: GSAK 7.7.0.109 update problem
I had a different issue where OZI Explorer exports caused GSAK to crash. Clyde has advised that he has fixed this but it's yet to be released so my automatic stuff isn't working at the moment.
The 7.7 improvements are generally good. Particularly column renaming and I've found my macros are running a lot quicker with the new database changes
Edit: I take that back, Clyde has now released a patch which addresses my issue ... http://gsak.net/board/index.php?showtopic=14859
The 7.7 improvements are generally good. Particularly column renaming and I've found my macros are running a lot quicker with the new database changes
Edit: I take that back, Clyde has now released a patch which addresses my issue ... http://gsak.net/board/index.php?showtopic=14859
- riblit
- It's the journey.
- Posts: 3444
- Joined: 04 April 03 6:30 pm
- Location: Land Grant of John Campbell
Re: GSAK 7.7.0.109 update problem
The upgrade will backup the data but you will lose the old program.blossom* wrote: Does all this mean I should back something up before I update my gsak? Or is there something I can check to make sure it doesn't go wrong for me? I'm not all that great at fixing things on my computer if they go wrong
To be really safe you should copy the complete GSAK directory and all subdirectories. Easy if you are running XP, a bit problematic if you are running vista as vista moves things around a bit.
If you have XP open the "Program Files" folder, find the GSAK folder, right click on it and drag. Select copy here from the menu when you release the mouse button. This will copy the GSAK folder and its sub folders to a folder called "copy of GSAK". If you have a problem you can delete the GSAK folder and rename the copy on GSAK.
Re: GSAK 7.7.0.109 update problem
Thanks so much. I have copied the whole gsak folder and contents so I now feel comfortable upgrading to the newer versionriblit wrote:The upgrade will backup the data but you will lose the old program.blossom* wrote: Does all this mean I should back something up before I update my gsak? Or is there something I can check to make sure it doesn't go wrong for me? I'm not all that great at fixing things on my computer if they go wrong
To be really safe you should copy the complete GSAK directory and all subdirectories. Easy if you are running XP, a bit problematic if you are running vista as vista moves things around a bit.
If you have XP open the "Program Files" folder, find the GSAK folder, right click on it and drag. Select copy here from the menu when you release the mouse button. This will copy the GSAK folder and its sub folders to a folder called "copy of GSAK". If you have a problem you can delete the GSAK folder and rename the copy on GSAK.
- gmj3191
- 7500 or more caches found
- Posts: 1316
- Joined: 22 April 03 12:37 am
- Location: Sandringham, Vic Garmin Oregon 650
Re: GSAK 7.7.0.109 update problem
I had an issue when upgrading in that it couldn't delete a temp file as it was locked by GSAK.
Killing GSAK and restarting the upgrade wouldn't fix it
Rebooting and repeating the upgrade fixed it.
Killing GSAK and restarting the upgrade wouldn't fix it
Rebooting and repeating the upgrade fixed it.