EViews.com

I think you're out of luck.

Create a new coefficient vector (not a vector, but a coef) called G, then use g instead of c

Use instead of

The EViews implementation of X-13 allows you to assign a workfile series as a user-variable in the X-13 pre-adjustment regression. You can create at calendar variable similar to those built in to X-13, but supporting you specific calendar. Recommend reading the X-13 documentation to see how they def...

Sounds like the Python code is creating a file that isn’t 100% compliant with the xlsx file format. Excel is able to handle the lack of compliance better than EViews is.

Easiest fix might be to save as csv from Python instead.

Is this consistently happening? I just tried, and seemed to retrieve all?

There's nothing built in that will do it, you'll need to write your own code.

No, just install the latest patch.

I can't really see how that worked in EViews 12 (and I ran it in 12, and the same behaviour as 13 occurred).

But, you probably want to use the colheadnames=( ) argument of the important statement to say which rows contain name information.

Could you provide the csv?

It looks like you're running the patch installer, rather than the full application installer.

Appears to work ok for me. Is there something else you're doing?

More specifically, when issuing a command, EViews presumes you're sat there willing to input something, so if there is a doubt about what's going on, EViews is more willing to prompt you with some options. If you're running a program, EViews assumes you don't want to be prompted, so goes with a defa...

Try running it in an program, not as a command.

Seems to work fine for me. Is your copy of EViews up to date?