In the client/server model, when using the low-level functions RETREC() and RETVREC() (ReleaseData and ReleaseVData), unexpected record offsets beyond the 4GB boundary could be marked deleted and available for reuse because the high word set by ctSETHGH() was not being set properly. The logic has been improved to correct this. Note this is a rare situation as the low-level API imposes additional network overhead, so very few applications are expected to be impacted by this issue.