If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Validation Rules
"Jason Wills" wrote in
: but i would like to make sure that people don't type in anything in the field rather than use the lookup That is not a job for a ValidationRule, it's a job for Referential Integrity. Creating a relationship means "this field can only contain a valid value from that table". As long as that rule is kept it doesn't matter how the value gets the e.g. combo box, text box, VBA, Excel, MS Query etc etc etc. B Wishes Tim F |
#2
|
|||
|
|||
Validation Rules
thanx for your responses, referential integrity unfortunately didn't work
for me, the list was already populated with other stuff, so i couldn't force the integrity, but i understand that if i had designed it like this to start with then i wouldn't have had the problem now. fortunately the other post worked great, (setting the LimitToList property to true).. thanx both of you regards Jason "Jason Wills" wrote in message ... I would like to create a validation rule on a lookup field in a table..... the lookup table works fine, but i would like to make sure that people don't type in anything in the field rather than use the lookup.... as this would add a new record in the table with a name that i dont have control over Any ideas would be great... Cheers Jason |
Thread Tools | |
Display Modes | |
|
|