2.03 and 2.12 glitches (AREV Specific)
At 15 DEC 1998 07:41:54PM Warren wrote:
Since a client of mine planning on switching from a Novell network to NT I'd have to upgrade there ARev 1.16 to a minimum of 2.03 I thought I'd test upgrading their application to see what glitches there are and to decide whether to upgrade to 2.03 or 2.12 as well as being able to to give an intelligent estimate as to cost.
From my experience in the past going to 1.1x to 2.03 can be somewhat tricky for the main reason that many of the system subroutines in 2.03 would 'step' on system variables like @record, @id, and @dict.
What I found:
2.03:
- Hard coded 'F' type popups - POP.UP blows up with a non-numeric error if the field number in the field format parameter is null.
- For some reason Quick/Rightdex keeps blowing up in a summarization program with a 'corrupted quick/rightdex record, fix with select or list on the file' message during writes to this file. Reinstalling rightdex to the file has no effect. Error occurs only in this program (complex uses v119).
2.12:
- The rightdex problem is not there but relational indexing is 4 to 10 times SLOWER than 1.16 or 2.03. This can be evidenced during file writes that update the related field AND during index rebuilds. I tried removing and reinstalling indexing altogether on this file with no difference in performance.
Since the application is depends heavily on the relational index I'll have to go with 2.03 due to the performance hit. The rightdex can be removed from the file as it is not necessary. Since this is a legacy application that is slated to be phased out in a few years the client doesn't want to spend a great deal of time and money on the migration so 3.12 and OpenInsight are out of the equation.