1st, all those options are attributes of entity "payment type" thus they ought to be records in tblPmtType, not fields in tblPayments. Improper normalization will continue to thwart you as it seems to be the case here. The litmus test is "If I need another payment type must I add another field?". If the answer is yes, the design is wrong.
The error message also suggests that the field is a lookup field in your table, which is another issue if true. While you see CASH, the actual relevant value is a number that corresponds to the position in a hidden table, like 1. This would explain your issue, I think. You can a) pass the correct number b) use the .Value property in the field (as in NameOfField.Value or c) do away with the lookup field.
Last edited by Micron; 06-08-2019 at 12:38 PM.
Reason: spelin and gramur
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.