hfs55 wrote:
B: use IS (interactive schedule) to get the areas, then export to excel and do cost calcs there. This works but it would be great to have something that is live, and less manual.
Unfortunately, even this non-live option does not give correct results as nothing - lists nor element schedules - will report the correct height of a column trimmed by a solid element operation. I had not tested this in 16 yet, and was hoping it was fixed, but sadly it still is not. Seeing this major flaw, I didn't spend any time testing all other elements to see which ones report correct scheduling values.
ArchiQuant uses the List Scheme technology, but with a friendlier interface.
The information obtained from the Windows ODBC driver will be no more accurate than what you can obtain within AC. E.g., column heights will not be correct if involved in SEOps. But, it does allow for live connection to an estimation database. The downside is that you would have to use the ID or some other field to distinguish how an element should be computed. At least with List / Components schemes, you can assign the desired material formulas per-element within AC.
I subtracted a hole from a slab via SEO and the List Scheme, ArchiQuant and Element Schedule (interactive) all reported the modified volume correctly. So, your asserting that SEO are not taken into account by the list method is not correct. Again, nothing calculates columns correctly - and I haven't tested beyond slab just now to break things down into which elements are computed correctly (SEO-wise) and which are not.
Karl
One of the forum moderators
AC 28 USA and earlier • macOS Ventura 13.7, MacBook Pro M2 Max 12CPU/30GPU cores, 32GB