<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Stylus BT";
panose-1:2 14 4 2 2 2 6 2 3 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:"AvantGarde Bk BT";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Jude/Aaron,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>When I’ve run into this circumstance I’ve taken it as great justification to go back and simplify the model. If that’s not out of the question considering your timeline and requirements for accuracy, I would definitely advise carefully assessing whether you can define things in a simpler fashion. Attached recent discussion with James Chueh seems to parallel your situation and may help you brainstorm a few ideas. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I’ve never done this due to sheer model size (only on smaller projects), but I have advocated “splitting the model” for time-efficiency, and that may be a good strategy for you in this instance. Look for an importing mini guide thread I posted in the archives.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>The concept is to build up parallel model files that are intentionally structured/named in a fashion to be import-able into each other. You may find splitting your building in two will be functionally manageable with the eQuest interface, and if/when you need to model both halves of the building together you can go through the importing hoops. Before going far down this path I would personally give this strategy a test run to be sure the importing feature doesn’t cause unique issues due to model size… uncharted territory!<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>~Nick<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='color:#1F497D'><img width=119 height=37 id="Picture_x0020_1" src="cid:image001.jpg@01CC9009.D80D2FB0" alt="cid:489575314@22072009-0ABB"></span><b><span style='font-family:"Stylus BT","sans-serif";color:#2D4D5E'><o:p></o:p></span></b></p><p class=MsoNormal><b><span style='font-family:"Stylus BT","sans-serif";color:#2D4D5E'><o:p> </o:p></span></b></p><p class=MsoNormal><b><span style='font-size:12.0pt;font-family:"Stylus BT","sans-serif";color:#2D4D5E'>NICK CATON, P.E.</span></b><b><span style='font-size:12.0pt;font-family:"Stylus BT","sans-serif";color:#2D4D5E'><o:p></o:p></span></b></p><p class=MsoNormal><span style='font-size:7.5pt;color:#CC9900'>SENIOR ENGINEER<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:7.5pt;color:#CC9900'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>Smith & Boucher Engineers</span><span style='font-size:7.5pt;font-family:"Times New Roman","serif";color:#CC9900'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>25501 west valley parkway, suite 200<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>olathe, ks 66061<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>direct 913.344.0036<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>fax 913.345.0617<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><a href="www.smithboucher.com" title="blocked::www.smithboucher.com"><span style='font-size:10.0pt'>www.smithboucher.com</span></a></span><u><span style='font-size:10.0pt;color:blue'> </span></u><span style='color:#1F497D'><o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> equest-users-bounces@lists.onebuilding.org [mailto:equest-users-bounces@lists.onebuilding.org] <b>On Behalf Of </b>Dahlstrom, Aaron<br><b>Sent:</b> Friday, October 21, 2011 3:28 PM<br><b>To:</b> Chakraborty, Jude; equest-users@lists.onebuilding.org<br><b>Subject:</b> Re: [Equest-users] Equest freeze and Spreadsheet refresh error<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>We have definitely have had models that were so large we couldn’t make changes in the spreadsheet view.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>It’s tedious but one option is to make any changes needed in the dialog boxes.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>AD<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'><o:p> </o:p></span></p><div><p class=MsoNormal style='line-height:150%;text-autospace:none'><b><span style='font-size:9.0pt;line-height:150%;font-family:"Verdana","sans-serif";color:gray'>Aaron Dahlstrom , PE, LEED® AP</span></b><o:p></o:p></p><p class=MsoNormal style='line-height:150%;text-autospace:none'><b><span style='font-family:"AvantGarde Bk BT";color:#17365D'>In P</span></b><b><span style='font-family:"AvantGarde Bk BT";color:#619428'>o</span></b><b><span style='font-family:"AvantGarde Bk BT";color:#17365D'>sse</span></b><span style='font-size:9.0pt;line-height:150%;font-family:"Verdana","sans-serif";color:gray'> – </span><span style='font-size:8.0pt;line-height:150%;font-family:"Verdana","sans-serif";color:gray'>A subsidiary of</span><span style='font-size:9.0pt;line-height:150%;font-family:"Verdana","sans-serif";color:gray'> </span><b><span style='font-size:9.0pt;line-height:150%;font-family:"Verdana","sans-serif";color:#CC0000'>AKF</span></b><span style='font-size:9.0pt;line-height:150%;font-family:"Verdana","sans-serif";color:gray'>| 1500 Walnut Street, Suite 1414, Philadelphia, PA 19102 </span><o:p></o:p></p><p class=MsoNormal style='line-height:150%;text-autospace:none'><span style='font-size:9.0pt;line-height:150%;font-family:"Verdana","sans-serif";color:gray'>d: 215-282-6753| m: 267-507-5470| In Posse: 215-282-6800| AKF: 215-735-7290</span><o:p></o:p></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";color:gray'>e: ADahlstrom@in-posse.com | in posse web: <a href="http://www.in-posse.com/">www.in-posse.com</a> | akf web: <a href="http://www.akfgroup.com/">www.akfgroup.com</a></span><o:p></o:p></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";color:gray'> </span><o:p></o:p></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";color:gray'> </span><o:p></o:p></p></div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Times New Roman","serif";color:gray'> </span><span style='font-size:12.0pt'><o:p></o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> equest-users-bounces@lists.onebuilding.org [mailto:equest-users-bounces@lists.onebuilding.org] <b>On Behalf Of </b>Chakraborty, Jude<br><b>Sent:</b> Friday, October 21, 2011 1:41 PM<br><b>To:</b> equest-users@lists.onebuilding.org<br><b>Subject:</b> [Equest-users] Equest freeze and Spreadsheet refresh error<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Dear all,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I am trying to model a high rise 25 floor courthouse building with multiple shells (12) and many zones (near 500). I have used floor multipliers where I could to make the model simpler but it ended up with 60,000 lines and about 7500 components. The .bdl file doesn’t show any error and I have also run a default simulation, which took its time but gave results without any errors. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Now in the detailed interface, equest freezes whenever I try to make changes on anything or create a new schedule. Also when I go to the building shell spreadsheet, it shows this “Spreadsheet refresh error” with the following text "Selection list exceeds maximum length of 65,500 characters (98,339required). Notify program support representative". <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN>Does it mean that I need to reduce number of spaces/zones or divide my building into two separate files? Any idea how to solve this problem?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN>Jude.</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><br clear=all>This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unintended recipients are prohibited from taking action on the basis of information in this e-mail. E-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered without the knowledge of the sender or the intended recipient. If you are not comfortable with the risks associated with e-mail messages, you may decide not to use e-mail to communicate with In Posse. <o:p></o:p></span></p></div></body></html>