Question-and-Answer Resource for the Building Energy Modeling Community
Get started with the Help page
Ask Your Question

Why does IDF Editor issue error "Run-time error '9': Subscript out of range," aborting on Save-as?

asked 2018-03-10 01:21:53 -0500

Molly Curtz gravatar image

updated 2018-03-10 01:36:26 -0500

I have an IDF file that I exported from Design Builder (v. The Version listed in the IDF is "". I would like to open this file in IDFEditor, and save it to get the objects formatted (grouped by class and in the IDF editor format.) When I open it with the IDFEditor v8.6.0, I got a warning that the file format is incompatible with the .IDD file being used, and with the IDFEditor version. I edited the Version to be "8.6" in my text editor, and that warning ceased. The IDF file appears to run fine using EPLaunch v8.6.0 (I am running it now: it was read with no issues....and still simulating fine so far).

BUT, when I try to save the file, it aborts during the process with the error: "Run-time error '9': Subscript out of range", once I click "Okay" on that error, the IDFEditor quits. (I can open the new IDF file that I was attempting to save, and it does contain a incomplete portion of the IDF.

Any ideas how I can solve this?

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2018-03-10 10:16:42 -0500

Molly Curtz gravatar image

updated 2018-03-14 23:55:18 -0500

I did some experimentation and found that once I split the IDF file into two halves (in a text editor) I was able to save each half separately in the IDF Editor without issue. This is a workable solution for me at this time.

When I recombine the two halves that were saved by IDF Editor, the error occurs again.

@JasonGlazer identified that the problem was due to IDF editor running out of memory since there were a huge number of schedule:compact objects in the file. Solution was to edit the .IDD file to reduce the number of fields allocated to each one of these, to a number that will be enough fields to accommodate each of the schedule:compact objects you will have (i.e. define it with enough fields for the longest schedule:compact object you think you will ever need), but not so many that IDFEditor runs out of memory. Refer to comments below from Jason for further info.

edit flag offensive delete link more



Molly, could you send me file? I would like to test it in the debugger and see what the problems is. If it is just a fixed size array in IDF Editor that is the problem, I will try resizing it. jglazer at gard dot com

JasonGlazer gravatar imageJasonGlazer ( 2018-03-12 08:10:08 -0500 )edit

This was an extremely large file with a huge number of Schedule:Compact objects. When I tried to open it in the debugger, it was running out of memory (it is an old 32-bit application). As a workaround, I changed the energy+.idd to have fewer fields for the Schedule:Compact object and we were able to open and do a save as on the file.

JasonGlazer gravatar imageJasonGlazer ( 2018-03-14 07:14:53 -0500 )edit

Thanks for the help @JasonGlazer!

Molly Curtz gravatar imageMolly Curtz ( 2018-03-14 16:17:11 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer


Question Tools

1 follower


Asked: 2018-03-10 01:21:53 -0500

Seen: 32 times

Last updated: Mar 14