>>My workaround was to add 'LPARAMETERS tlCurrentRecord'
>
>I beat you to it. This bug has been reported and should be in the next release.

Why am I not surprised that it's been seen?