Hi all,
Well it's been hell of a long time since I last did a database and used this forum way back in 2003/4, so Hi to all the newbies and Hi to all those who are still here from 7 or so years ago.
I'm struggleing to get what I want from user input selection.
For ease I want to use an option box rather than a combo for values as follows:
This table is called PAID_TYPE
ID:
So as you expect it stores the value in the reservations TABLE field 'PAYABLE' as a number however when I run a query I can't get just the value and want the TEXT output as this will be output to an invoice.
Would I have to use Choose for within the Query, sorry probably easy but not getting the answers I expect from my testing.
Thanks in advance
Ian
After thought - Would it be best to have an unbound option group and depening on the input build code to fill in the text in the field I want. This code I would have no problem with, but is it good planning or bad design????
Well it's been hell of a long time since I last did a database and used this forum way back in 2003/4, so Hi to all the newbies and Hi to all those who are still here from 7 or so years ago.
I'm struggleing to get what I want from user input selection.
For ease I want to use an option box rather than a combo for values as follows:
This table is called PAID_TYPE
ID:
Payable
1Paid
2Cancelled
3N/A
4Payable on Arrival
So as you expect it stores the value in the reservations TABLE field 'PAYABLE' as a number however when I run a query I can't get just the value and want the TEXT output as this will be output to an invoice.
Would I have to use Choose for within the Query, sorry probably easy but not getting the answers I expect from my testing.
Thanks in advance
Ian
After thought - Would it be best to have an unbound option group and depening on the input build code to fill in the text in the field I want. This code I would have no problem with, but is it good planning or bad design????