Import Crash Bug File Path

[CharlieEVIEWS]

Come across the same bug a couple of times with a couple of different projects in the last week: In EV9, when using the import command, if the filepath doesnt exist, i invariably get the deadly 'EViews has stopped working' crash.

[EViews Steve]

Can you provide one of your typical IMPORT commands that causes the crash? I can't seem to reproduce it...

[CharlieEVIEWS]

Hi Steve,

A little further analysis shows that the cause of the bug is when there is a 'space' in the non-existent file-path. For example, where the folder 'nopath' does not exist, the following does not cause a crash:

Code: Select all

import C:\nopath\data.xls @freq m 1959m1

but this does:

Code: Select all

import C:\no path\data.xls @freq m 1959m1

My memory is really terrible, but this might actually be a bug not related to EV9. Let me know if I can be of any further assistance.

Charlie

[EViews Steve]

Charlie:

I couldn't reproduce the issue. I suggest you download the latest patch (we'll release one sometime today) and then try again. If you encounter a crash, see if you can create an EViews program to reproduce the issue.

Thanks,

Steve

[CharlieEVIEWS]

Hi Steve,

I just encountered the bug again in a seperate instance where I was trying to import a workfile which didnt exist in the directory. This is what the actual bug is, as in the MWE (below), it is trying to open c:\no.wf1, which doesnt exist.

The MWE which I used eariler to generate the example was:

Code: Select all

wfcreate m 1959m1 2003m12 import C:\no path\data.xls @freq m 1959m1

But as you suggest, I will try again after the patch goes in.

[startz]

Just for the record, I can duplicate Charlie's bug every time I try it. Oddly, the crash comes on dismissing the dialog when import can't gind the file.

[EViews Steve]

Ok, I was able to find the issue. It'll be fixed in today's patch (will be released in a moment).

[CharlieEVIEWS]

Works just fine now. Thanks Steve!