You must have administrator rights to access this feature.
This feature may not be available in every package. Not sure if you have this feature or you want to learn more about it? Send us a message at email@example.com.
A recordset is a collection of fields that relate to a particular asset. The recordset and field structure of the database is found in Structure Manager.
There are different types of recordsets in the Cartegraph database.
A parent recordset contains information about a particular feature:
- Typically, a parent recordset contains the ID field.
- Requests, Tasks, Work Orders, Markings or Signs are examples of a parent recordset.
Create a recordset to add fields to the database that contain information not included in the original Cartegraph software. This procedure adds a child recordset to an existing parent recordset in your database. This is helpful when you need to create information where there will be many records that relate to a single parent record. For example, adding guard rail records to pavement segments.
Child recordsets are collections of fields that relate to a parent record. Each parent record may have many child records. Inspections are a typical example of a child recordset. Over the years, inspection records accumulate. Each inspection record belongs with a particular parent. For example, the inspection record includes several data fields, date, rating, and inspection type. The collection of inspection records is the child recordset for that particular asset.
Share recordsets to view part of one recordset to another. For example, sharing a Sidewalk recordset to work with sidewalks with another asset. Shared recordsets are indicated in the structure view of Structure Manager with . Tasks is an example of a shared recordset that is under every asset recordset.
A Library is another special kind of recordset:
- Libraries are normally the source of data used in a list box.
- Libraries are often shared by more than one asset.
- Some libraries may include predefined startup data.
- All libraries can be populated with data that matches your organization.
Recordsets cannot be deleted if:
- The recordset is a top-level recordset such as Bridges, Tasks, or Labor.
- The recordset is marked as system.
- A child recordset beneath the recordset is marked as system.
- A field in the recordset is marked as system
- A field in the recordset is the target of a lookup
- If there are any views associated with the recordset, those will be removed on delete of the recordset.
If you delete a recordset, it is permanently destroyed, along with all data records.