Hi all,
I have a totally weird analysis problem:
I have a file with a composite key consisting of 4 numeric fields (Tp+Vuosi+Kk+Rptyyppi), all of which are also separate duplicate keys.
The composite key used allow duplicates, but I changed it to be unique. The file also has a unique autonum key.
Then I modified the file to match the analysis.
This file is used to store the results of monthly reports during a monthly system maintenance batch process, which is managed in its own window.
Now, when I start the program, my file opening process opens it without any problems, and I can use the file, except after doing a complete backup and re-opening the main program as follows:
As the first stage of the monthly maintenance process I have a complete backup process of the system which is done by closing the program and calling a separate "BackUper" program which copies the global data directory and the local program directory to another media.
When the complete backup is done, the BackUper re-opens the main program and re-opens the files with the same file opening process, and NOW WD fires this totally weird error, before it re-opens the maintenance process window:
//--------------------------------------------------------
Error at line 69 of Global Procedure OpenAllFiles process.
HCreationIfNotFound function called.
The description of the logical file <RAPORTTI> stored in the analysis is not compatible with the one stored in the physical file <D:\TYÖMYYRÄDATA_FT\Raportti>. Unable to access the file.
The <TpVuosiKkRptyyppi> item of <RAPORTTI> file is unique key in the file but it is not unique key in the analysis.
The descriptions are not compatible, duplicate errors may occur during the additions.
//--------------------------------------------------------
The weirdest thing here is that in the analysis the key is actually defined as unique! Or at least that's how I defined it and that's how it looks like in the analysis editor! But maybe it internally allows duplicates?
I really could use some hints to fix this problem!
I already tried deleting the composite key from the file description and then re-entering it, and re-modifying the file, but it does not help.
I also tried deleting the file (in test database of course), but when the file was re-created by the file opening process, the same problem exists after full backup.
Best regards
Ola
I have a totally weird analysis problem:
I have a file with a composite key consisting of 4 numeric fields (Tp+Vuosi+Kk+Rptyyppi), all of which are also separate duplicate keys.
The composite key used allow duplicates, but I changed it to be unique. The file also has a unique autonum key.
Then I modified the file to match the analysis.
This file is used to store the results of monthly reports during a monthly system maintenance batch process, which is managed in its own window.
Now, when I start the program, my file opening process opens it without any problems, and I can use the file, except after doing a complete backup and re-opening the main program as follows:
As the first stage of the monthly maintenance process I have a complete backup process of the system which is done by closing the program and calling a separate "BackUper" program which copies the global data directory and the local program directory to another media.
When the complete backup is done, the BackUper re-opens the main program and re-opens the files with the same file opening process, and NOW WD fires this totally weird error, before it re-opens the maintenance process window:
//--------------------------------------------------------
Error at line 69 of Global Procedure OpenAllFiles process.
HCreationIfNotFound function called.
The description of the logical file <RAPORTTI> stored in the analysis is not compatible with the one stored in the physical file <D:\TYÖMYYRÄDATA_FT\Raportti>. Unable to access the file.
The <TpVuosiKkRptyyppi> item of <RAPORTTI> file is unique key in the file but it is not unique key in the analysis.
The descriptions are not compatible, duplicate errors may occur during the additions.
//--------------------------------------------------------
The weirdest thing here is that in the analysis the key is actually defined as unique! Or at least that's how I defined it and that's how it looks like in the analysis editor! But maybe it internally allows duplicates?
I really could use some hints to fix this problem!
I already tried deleting the composite key from the file description and then re-entering it, and re-modifying the file, but it does not help.
I also tried deleting the file (in test database of course), but when the file was re-created by the file opening process, the same problem exists after full backup.
Best regards
Ola