EViews.com

By default, if you specify a single cell during an import, EViews tries to expand it to include all cells with data to the right and below that point. We can't easily change that as many users depend on that functionality for automatically determining data ranges in an unknown source spreadsheet. Bu...

Were your lab machines recently updated to new physical boxes? Swapping out the host machine can lead to licensing issues for a lab license. When an EViews lab license is given out to a client machine, it becomes "tied" to that machine and cannot be used elsewhere after EViews has run for ...

Kun0:

Please email me at steve@eviews.com and reference this posting. I'll send you instructions on how to send us your workfile so we can look into it.

Steve

Thanks for the detailed info.

We were able to reproduce the error and a fix has been made. It will be available in the next EViews 9 patch after today.

Steve

By the way, Jason just pointed out that when the title bar is down to 1 pixel length, you can always just scroll the master scrollbar "up" so that it brings the whole title bar into view again.

The graph view being too large for the window is an issue -- but, like you said, I'm not sure how we would solve it. I'd rather not resize a window for each different view you select... About the drag "bug", I don't think it's actually a bug. There's no way to drag a window's title bar com...

There are a few suggestions I can make: First, you can shorten the height of the command window. Second, you can "unpin" the command window so it pops in and out whenever you need it by un-clicking the pin icon in the top right of the command window. This will let you use more of the scree...

The resize option on the second import should've worked, but I can understand why it doesn't for a dated panel -- resizing a dated panel can be very complex and all the data conditions have to be exactly correct on the second source file for it to theoretically work. I don't know how many rows of da...

That's probably your best bet. Though once you have the data from any of our Get methods, it's easy to transpose the data manually or have Excel do it for you -- I'm guessing there's a lot of tranpose options within Excel.

Ok, a few things to discuss here... First, if you call GetApplication and pass a 1, this means ExistingOrNew. So if EViews happens to be already running, this code will connect to that instance and basically take it over. This might not be a "safe" thing to do as the user might be in the m...

If you resize the source workfile, add more data, and save the workfile, the linked data column in Excel should also grow the next time it performs an update.

The Excel data links that our add-in creates are simply OLEDB data connections. The add-in just helps you create these. Once created, the link is maintained and updated by Excel. If you access the connection string property of your OLEDB connection object, you can parse it to find the full path to t...

Well I looked into the FETCH captured command and it wasn't generating the correct conversion option. I've changed this so the next patch should fix it. This means if you manually COPY an object in the database window, then do a PASTE special into a workfile window, then in the dialog select a speci...

Sorry, but I need a few more details. When you performed the fetch, did you do it to a workfile with a matching frequency or did you do it to a higher frequency workfile? Then how did you manually do the frequency conversion afterwards? Was there another workfile page with the target frequency invol...

Were you performing a fetch when you did the conversion, or were you converting a series object already in your workfile to another page with a higher frequency?