Avoid usage of Rec.Count() if possible

[christophstuber]

Count can be one of the most expensive database operations on large tables. I often see examples like this in code:

Checking for no records:

if Rec.Count() = 0 then

Should be replaced by:

if Rec.IsEmpty() then

Checking for any records:

if Rec.Count() > 0 then

Becomes:

if not Rec.IsEmpty() then

Checking for exactly one record:

if Rec.Count() = 1 then

Refering to https://vjeko.com/2017/03/08/the-if-count-1-conundrum/

if Rec.Find('-') and (Rec.Next() = 0) then

Checking for more than one record:

if Rec.Count() > 1 then

if Rec.Find('-') and (Rec.Next() <> 0) then