ODBC Export Change in V7 - For Better or Worse ?

[Phil Palmer]

We have been extensively utilizing the ODBC export facility from Revit since V4.5.
I have a web developer who has created a web based application for our FF&E scheduling and management for mainly school projects.

Problem now :-
In the past ALL family tables included the RoomID within their respective tables so we have built many (loads) of scripts on that basis.

When you now export to ODBC in V7 the RoomID filed is no longer in each family category table and there is now 1 complete table (RoomAssociations) listing ALL families linking to the actual roomID

This is a MAJOR change in the ODBC exported tables and I think a pretty inefficient way of handling this data. (for example our library has over 6000 records in that table)

Has anyone else came across this ?

[David Conant]

Before this change, ODBC export had no concept of phase as applied to rooms. It simply used the room arrangement of the last phase. In Revit, rooms are phase specific. For every phase, each room has an independent identity even if its boundary has not changed. The new system reflects this. There is a table that records all of the rooms defined for the project and which phase that room exists in. The associations table defines what rooms an element is in (there can be one for each phase). The end result is the ability to create phase specific reports that include rooms and their associated contents.