Hello,
We attempted our upgrade from A5V6 to A5V7 this evening. Things did not go as smoothly as we had hoped. ;) We run shadow databases on all the runtime clients, but hit errors as we tried to create the first shadow on the first upgrade machine. Initially, the shadow was created but still claimed to be the master database. The main menu form displayed but none of the buttons to access other forms worked ("form not found"). The Control Panel was completely blank save for one operation. Trying again on another machine, we hit the "SmartHeap Library: MEM_BAD_POINTER" error.
This error came up many, many times, and even if we could view the main menu form we were not able to go any deeper than that.
Turned out, we cannot create a shadow on the runtime version when anyone else has the database open. This was not the case in A5V6, and a pretty big stopping point for us right now. (ie We've aborted the upgrade and rolled back to A5V6 on the initial test machines.)
We did some testing with A5V7, and we could refresh two shadows at the same time without errors. The problem was solely with the creation of the shadow. For some reason, the application wanted complete control of the database for the duration.
Has anyone seen this error before, and has a workaround been found?
(Note: this is with the latest patched version of Alpha Five V7.)
We attempted our upgrade from A5V6 to A5V7 this evening. Things did not go as smoothly as we had hoped. ;) We run shadow databases on all the runtime clients, but hit errors as we tried to create the first shadow on the first upgrade machine. Initially, the shadow was created but still claimed to be the master database. The main menu form displayed but none of the buttons to access other forms worked ("form not found"). The Control Panel was completely blank save for one operation. Trying again on another machine, we hit the "SmartHeap Library: MEM_BAD_POINTER" error.
This error came up many, many times, and even if we could view the main menu form we were not able to go any deeper than that.
Turned out, we cannot create a shadow on the runtime version when anyone else has the database open. This was not the case in A5V6, and a pretty big stopping point for us right now. (ie We've aborted the upgrade and rolled back to A5V6 on the initial test machines.)
We did some testing with A5V7, and we could refresh two shadows at the same time without errors. The problem was solely with the creation of the shadow. For some reason, the application wanted complete control of the database for the duration.
Has anyone seen this error before, and has a workaround been found?
(Note: this is with the latest patched version of Alpha Five V7.)
Comment