Oké, thanks for the explanation, luckily its not another Garmin bug.