ProConcrete Partlist Database Details

The reporting tool reads ProConcrete object information from an Access database rather than directly from the design file. Supporting Item Types in a ProConcrete report extended the ProConcrete database structure.

A field is added to a partlist table for every Item Type that is attached to an object in the table (as marked in red rectangles in the above image).

The field name is based on the Item Type name. It is prefixed with "ItemType" to differentiate it from other fields.
- In the viewRebarPartlistDetail view, names for fields for Item attached to bars are prefixed with "BarIType" to differentiate them from the fields for Items attached to concrete objects.
The field value is a unique identifier for the first object that was found with the attached Item.

Note: The Item Type fields are not added to the ConcretePartlist table-the concrete "summary" table.

A table is added to the database for each Item Type field that was found attached to an object-the orange rectangle in the image above. Each record in the table is a unique Item (set of property values).

The table name matches the partlist field name.
The first field-ItemTypeKey-is used to join the Item (set of property values) to one or more objects in a partlist table.
The remaining fields are named for the Item Type properties. The field values are the individual property values as strings. The fields can hold up to 255 characters.

When Item Type fields are added to tables for Rebar, a field named NoItemTypeBarGrouping-the green rectangles in the image above-is added first. The values in this unpublished field are used to regroup the bars (correctly) when all item values are not shown in the ProConcrete report.

The List & Label field names are based on the Access table and field names. The Access naming restrictions cause the special character substitutions and truncations described in the Name Details section.

Multiple Database Support

The ProConcrete reporting tool can generate a report from more than one Access databases. A temporary database is created and rows from the partlist tables in each database are copied into the temporary database.

This feature was also extended to support Item Types.

The partlist tables in the temporary database contain fields for the union of Item Types found the partlist tables of the loaded databases.
The ItemTypeXxx tables are not copied to the temporary database. All Item values are read from the loaded database when needed.
The "key" values in the partlist tables in the temporary database are modified to record which database to find the Item values.