I'm using A2003 (yes, still). An accounting type form requires the "Type" be entered as either (numeric) 1, 11, or 2. On the same form, one of the three Yes/No fields must be checked as confirmation.
My hope is that I can use the "SetValue" action in a macro.
My first attempt (to set the "Assiniboine" field to "Yes" or "On"):
Item: [Forms]![DisbursementMade]![Assiniboine]
Expression: IIf([Forms]![DisbursementMade]![Type].[AfterUpdate]=1,Yes)
That isn't doing anything for me.
The default value for the "Type" field would normally be 1 (but that presumes the user will not skip past it without confirming it) so I have no default value.
The other two Yes/No fields would also be Set by the same logic: (if Type=11, [Bank]=Yes) (if Type=2, [PettyCash]=Yes)
Alternatively, I've tried the reverse approach: If [Assiniboine]=Yes, SetValue of [Type] to 1 so far without success. I'm not using VBA, since the bookkeeper changes from year to year and there is no Administrator. Although the computer has A2010, and can run an .mdb file with macros, successfully, making changes within A2010 produces an 'embedded macro' that isn't readable in A2003.
Any hope for me?:banghead:
My hope is that I can use the "SetValue" action in a macro.
My first attempt (to set the "Assiniboine" field to "Yes" or "On"):
Item: [Forms]![DisbursementMade]![Assiniboine]
Expression: IIf([Forms]![DisbursementMade]![Type].[AfterUpdate]=1,Yes)
That isn't doing anything for me.
The default value for the "Type" field would normally be 1 (but that presumes the user will not skip past it without confirming it) so I have no default value.
The other two Yes/No fields would also be Set by the same logic: (if Type=11, [Bank]=Yes) (if Type=2, [PettyCash]=Yes)
Alternatively, I've tried the reverse approach: If [Assiniboine]=Yes, SetValue of [Type] to 1 so far without success. I'm not using VBA, since the bookkeeper changes from year to year and there is no Administrator. Although the computer has A2010, and can run an .mdb file with macros, successfully, making changes within A2010 produces an 'embedded macro' that isn't readable in A2003.
Any hope for me?:banghead: