IMinute.DeleteRow Method

Sub DeleteRow( _ 
   ByVal firstRow As Integer, _ 
   Optional ByVal rowsCount As Integer = 1, _ 
   Optional ByVal recalcTask As Boolean = True _ 
)

This language is not supported or no code example is available.

void DeleteRow( 
   int firstRow, 
   int rowsCount = 1, 
   bool recalcTask = True 
)

This language is not supported or no code example is available.

Parameters

firstRow

int

The first row to be deleted (1-9999). The number is 1-based.

rowsCount

int

The number of rows to be deleted (1-10000), default is 1. You can set it to 10000, if you want to delete all rows. This way, you don't have to call GetRowsCount first, which may be quite slow.

recalcTask

bool

Optional. When true (default), the complete task will be computed at the end of deletion. When false, the task is flagged to be computed, leaving potential wrong values in totals until the task is computed.

This method requires the internal cache to be up to date, which is ususally the case, but there are some exceptions and you need to refresh it manually, see below.

Some methods use the internal cache for retrieving the minutes data. This is for performance reasons, especially, when one minute is accessed multiple times. These are (let's name them group 1): 
GetFieldValue, 
SetFieldValue, 
SetFieldValue, 
UpdateValuesConditionally, 
IEstimateVersion.UpdateMinuteValues.

And there are some methods that modify the minutes data, but they don't update the internal cache for performance reasons. These are (let's name them group 2): 
ClearRowValues, 
DeleteRow, 
InsertRows, 
InsertSetAtRow, 
InsertSetAtRow, 
GroupRows, 
UngroupRows, 
UpdateRowsFromDatabases.

So if you use the methods from group 2, you should update the internal cache manually before you call any method from the group 1. The cached data can be updated and retrieved with GetFullData method. You can update the cache also with the IWbs.Refresh method, but is it slower, because it does much more work.

See IMinute documentation for details about hidden "FreeField" field.

For historical reasons, this method doesn't throw any exception in case of any error. Instead, the error will be stored as a global error (if it was empty) in IGlobalErrors

.NET Framework