Establishes a relationship between rows and records.
Set_Property(OLECtrlEntID, "OLE.RowsToRecords", Value) |
Value can be any positive or negative whole number:
Default: 0
The RowsToRecords property is perhaps the most important property in the edit table when dealing with regular data. It allows you to specify the number of rows that a record spans. The SRP Edit Table uses this property to determine behavior.
By default, this value is zero. This means that there is no relationship between rows and records. This is the same as saying, "the edit table does not contain records." Edit tables with a RowsToRecords value of zero have irregular data, meaning any cell in any row or column may contain any kind of appearance, type, and data. Use this when you are using the Edit Table to simulate calendars, gant charts, etc.
Most of the time, you want the SRP Edit Table to handle regular data. Regular data is that which is consistent throughout the entirety of the table. For example, an edit table with the same data field from the same data table that is always in the same column contains regular data.
Setting this property to a value of 1, is not much different than setting it to zero when you are dealing with data. However, there's more to the table than data. The SRP Edit Table supports many visual enhancements. When you set this property to 1, you are telling the table that "every row must be the same because the table will contain repeating data." This causes other properties to behave differently because the edit table is making a proactive effort to keep the edit table consistent across all rows.
Furthermore, you can set this property to a value greater than 1. For instance, setting this property to 2 tells the table that "every 2 rows is one record, and every 2 rows must appear and act like a single record." When you set this property to a value greater than 1, you will immediately see the table make adjustments to rows headers, scrolling steps, new row counts, and column headers. It's like having word wrapping in your table, but I guess you should think of it as cell wrapping.