EViews.com

The command creates a workfile of type wf1 even when the default is set to wf2.

WF1 and WF2 file types are determined as the save point. When loaded, the workfile is the same data structure in memory as before.

You can save a workfile in WF1 format, and then save it again in WF2 format.

The point is that the command defaults to setting the save type as wf1. It probably should not. Much as I am personally fond of the wf1 file format, it is rather dated.

I'm confused. Are you saying the WFCREATE command defaults to WF1?

Our workfile save format default is controlled by a setting under General Options/Data Storage/Workfile Format (WF2): When you run the WFSAVE command, and you don't specify a file extension, the file is saved using the default workfile format type. And you can overwrite this default by either specifying a file extension or using the "type=wf2" option.

I think the issue is, if you do: It will create a workfile. If you then hit the "Save" button at the top of the workfile window, it will save that workfile as a .wf1 file, not a .wf2 file, even if your defaults are to save as .wf2.

Yes. That is the issue.

It'll be fixed in next patch.

Thanks.