EViews.com

Very strange. Now it works. I'm able to do the same thing on other xlsx files. Any thoughts on what makes this one different?

I think I'm missing something here. Are we talking about the excel file or the eviews file? Here are the combinations I can think of, and the outcomes that result from them: Attempt to import into eviews without Excel open: -Importing the data via script claims.prg - previously quoted error message ...

Ok, I recoded the query so dates are in chronological order. Same error.

Not sure what you mean by interactively. Can you clarify? I'm stumped too, this file is generated by Cognos report studio, saved on a network drive. Other reports generated in the same manner saved in the same location don't have this issue. The one distinction I can think of is that the date is sor...

Saved the file to my desktop, it was on a network mapped drive before. Exact same issue.

I can't actually. IT at work has pretty strict version control. I'd have to make a whole business case etc.

Same issue. If I run it with the excel file closed I get this error: Unable to determine date format of object CLAIM in [PATH] range=Page1_1!$A$1:$L$300 colhead=1 na="#N/A" @freq M @id @date(claim) @smpl @all If I open the excel file first and then run the program it's fine. Excel 2010 and...

That does seem best. Here you go.
Import code is as follows:

I have a program that imports data from an excel file. For some reason it will only successfully import the data if I have the excel file open prior to running the program. This is not an issue with other excel files. What I'd like to do as a hack-y solution is just call excel to open the file from ...

Thanks for the update. My company is quite slow about implementing patches. I'll verify the fix and report back when possible.

April 20 2015.

lmi_t, but the issue is the same with whatever series I try.

Sure. I've also attached the program I'm using
Right now it's using drop, which as you can see is cumbersome.

I'm trying to export a series to an excel file. pagesave(t="excelxml") %file_out @keep x creates an excel file with a date column and a series with a header that says "X" and then a whole series that is just X over and over if I do pagesave(t="excelxml") %file_out @drop...

No worries, I appreciate the help!