Is it possible to make a Read Only element writable if the Invoice_Date element falls within the current month?

What I'm trying to do is "lock in" invoice values once the month changes, so no one can go back and muck with the sales figures once they've been booked to our accounting system.  During the current month they can do whatever they like.

I have no problem with the ReadOnly() command, it's the test against this month that has me puzzled.
I tried this with no success:

// Sets the breakout elements to writable for Admin, and other users within the current month

IF ( ( @MONTH(Invoice_Date) = @MONTH(@Date)) AND (@YEAR(Invoice_Date) = @YEAR(@Date) ) OR (@Group = "Admin") )
THEN
	{
	ReadOnly(Portion_Rigging, 0)
	ReadOnly(Portion_Trans, 0)
	ReadOnly(Portion_Crane, 0)
	ReadOnly(Portion_Storage, 0)
	ReadOnly(Portion_Heli, 0)
	} 

Thanks in advance for any pointers.

Scott,

I think you may have parentheses issues in your conditional and you are not checking the combinations you think you are checking.

There's another issue. What you don't want to do is to make fields not read-only on a record that is read-only because of network record locking. You'll need to check on this first. To do so, check the readonly status of an element that is normally always editable. If it's locked, then the record is locked because of multi-user record locking. You then don't want to make any fields not read-only.

Infinity wrote on Oct 5^th, 2007 at 11:58am:


Yes, this caught me out recently. If I've the choice, I prefer to use Visibility to hide elements, rather than use readonly. It's less problematic. If you want to show what has been entered, and is now locked, then you've no choice.