Page 1 of 1

series omitted when storing to Aremos database

Posted: Tue Aug 01, 2017 11:04 am
by drew.sawyer
This bug can cause an error whereby some series are omitted when storing to an Aremos databank.

As currently written, the code below should produce the error.

The probability of error appears to be a function of 2 things:
(1) the alphabetical order of series being stored (the more out of order, the higher the probability of error)
(2) the number of series being stored (the more series, the higher the probability of error)

Thus, there are 2 independent ways to modify the code to prevent the error:
(1) Currently, %half2 is stored before %half1. If you reverse the order, the error should go away.
(2) Currently, there are 40 series in each half (total of 80). If you reduce it to 20 in each half (total of 40), the error should go away.

I am using this version:
EViews 9.5 (64-bit)
Enterprise Edition – Jul 11 2017 build

Code: Select all


wfcreate(wf=work, page=a) a 2000 2030


%half1 = ""

for !i = 11 to 50

  %half1 = %half1 + "a" + @str(!i) + " "

next


%half2 = ""

for !i = 51 to 90

  %half2 = %half2 + "a" + @str(!i) + " "

next


for %s {%half1} {%half2}

  genr {%s} = 1

next


if (@fileexist("bank.bnk") = 1) then

  dbdelete bank

endif

db(type=aremos) bank

store(d=bank) {%half2}

store(d=bank) {%half1}

close @db

dbopen(type=aremos) bank


Re: series omitted when storing to Aremos database

Posted: Thu Aug 03, 2017 11:10 am
by EViews Gareth
After some investigation, it looks like this is an issue with the Aremos API that we use to read/write Aremos files.

Unfortunately, as I'm sure you're aware, Aremos is an old, no longer supported product, so there isn't a way for us to fix the issue, or ask the Aremos team to do so.