Attempted Aliasing map crashes eviews

[dravenous]

Hey guys I am using Eviews 8.1 here. I am using the data registry function to pull data from an IHS Magellan bank. The data that I used comes with unfortunate mnemonics containing the @ symbol, so I was attempting to use aliasing mapping to correct this, enabling me to map a friendlier mnemonic to the ones with the @ symbol. When I bring up the database within eviews and click view->object aliasing, Eviews crashes and I am forced to close the program. Is there an intermittent step I am missing? I swear I have used this particular interface before. Any help you can give me would be much appreciated.

[EViews Jason]

Select options->general options and then select the File locations node.

Open in the Windows Explorer the path listed in the Ini File Path box.

In that directory, make a copy of the obalias.ini file. Next open obalias.ini with a text editor. You should find an entry for the Magellan database with one or more aliases below it. Remove all Magellan alias entries and save the file.

Now try running EViews and setting the alias again.

If EViews no longer crashes, please send to support@eviews.com the copy of obalias.ini.

[dravenous]

So randomly after I duplicated the error a dozen times or so, first on my pc, and then on a colleagues I returned to my pc, attempted to use the aliasing mapping and it worked...Without me altering anything. I have no idea why on the 14th time or so eviews decided not to crash. I didn't have to go into the .ini file as it corrected before I read the post above. Thank you for the prompt response, however, I wish I knew why the 14th attempt to access alias mapping was the lucky one.

[EViews Jason]

Did only happen on 1 day? Did it stop happening without you having to reboot or log out?

It is possible there may have been some corrupted memory.

[dravenous]

I don't often use the procedure, but it only happened on one day. It was the first time I had encountered the error. I did not log off the pc or reboot it, it corrected randomly without it. Eviews restarted multiple times during my attempts to access the aliasing mapping as it forced shutdown each time I hit view->object aliasing. It may have been corrupted data. At the end of the day it randomly started exhibiting the error and just as randomly stopped crashing.