I have an error with the new version 4.3.33 that didn't occurs in the early version, and using exactly the same scenarios.
We identify that the problem is in the sysettings, generating the error $338:
"**** LINE 1870 BATINCLUDE C:\Veda\Veda_FE\GAMS_WRKTIMES\XBASE.dd **** LINE 97 INPUT C:\Veda\Veda_FE\GAMS_WRKTIMES\conserva.RUN 128170 - **** $338"
When we put the sysetings in different positions in the solve form, the error mantains. And When we run without the syssettings the finshes but with no solution(but is expected it occurs).
22-07-2010, 02:55 PM (This post was last modified: 22-07-2010, 05:14 PM by Antti-L.)
It looks like you may be using the old-fashioned ADRATIOs a la MARKAL, and while VEDA now generates the UC_N name entries, it apparently generates '-' as the UC_N name for those old-style ADRATIO constraints, when the default interplolation options are applied in SysSettings.
I can recommend to start using the new UC_T facility for defining user constraints. However, I understand that the NEEDS models and other models using the old style constraints are still in widespread use and would benefit from having this bug fixed.
Thanks for the conclusive investigation Antti. This will be fixed later today.
But Joao, you should take Antti's recommendation and come to the UC_T world. The current DEMO has some examples. I should include a migration example as well...
I have a problem in synchronising SUB-Res files in the VFE end latest version 4.3.41. it shows a message "
-2147217900 (Microsoft) [ODBC Microsoft Access Driver] Number
of query values and destination fields are not the same"
and keep on comming even after clicking ok for some times for small files. I couldn't synchronise B-NewTechs file as the message keep on appearing. I have to restart the machine and when I open the VFE I get the message again.
It seems some sheetnames in your SubRES are unexpected. Remember that the SubRES sheetnames have to point to sectors of the model (that have been identified by the Base-year templates). You could add detail to sheetnames after "_". So, you can have <Sector>_<anything> as sheet names in the SubRES files. SubRES transformation file has no restrictions on sheet names.
Thanks Amit,We havn't changed any sheet name and they are still with the sector names and most of these SubRes files were not touched for long time.When I SYNC any of thses Sub_Res files I have this problem.
