423,851 Members | 1,043 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 423,851 IT Pros & Developers. It's quick & easy.

2101 The setting you entered isn't valid for this property

P: 22
Hello- I have an access 2010 db that i have been developing for almost a year. I have a list box, based on a query, that filters a form... for no explainable reason i now get the error message "2101 the setting you entered isn't valid for this property".

I have not changed any of the properties of my list box, or my form. The weird thing is, the folks that i am creating the db for have the exact same front end and back end, and they do not get the error message.

Also, if I click on a name in the list box I do not get the error, but if i type in the name i want to filter for (something I have always been able to do from the very beginning) i get the error.

After i click "ok" twice on the error message i am able to proceed with the name selection, and the form filters.

I have tried running the repair function for office pro from the "my computer, control panel," which didn't work, and i have compacted and repaired the file, which didn't work. Does anyone have any suggestions what to do?
Oct 5 '11 #1
Share this Question
Share on Google+
4 Replies


NeoPa
Expert Mod 15k+
P: 31,121
CharT:
for no explainable reason i now get the error message
You may not realise the reason or the cause of the change, but unfortunately we do rely on you to tell us what's different. Otherwise it's a bit like asking for details of your problem when all you've told us is that you have one. Frustrating to hear I know, but without any information other than the error message this won't be an easy one to help with. You may get lucky and someone remembers a similar situation, but otherwise we need the info from you.
Oct 5 '11 #2

P: 22
I wish I could answer your question! I haven't changed the properties of the list box, I have changed a few design features of the main form... i did however just figure out that it is only 1 record that produces the error, so I might just try recreating that record to see if that solves the issue.
Oct 5 '11 #3

P: 22
Okay- i figured out what the problem was... this may not apply to anyone else... but I have a field in the table that is the source of my form, that stores file paths that refer to images... when I copied an updated back end from my client to my local drive and linked to it, the image file path was trying to find their network drive and not my local drive and that apparently was the source of the error message. Once i changed the file path for the image to a file on my local drive, no error message... mystery solved!
Oct 6 '11 #4

NeoPa
Expert Mod 15k+
P: 31,121
Well done. You managed to work it out in the end. I do appreciate detecting such things can be very difficult at times. You got it sorted anyway :-)
Oct 6 '11 #5

Post your reply

Sign in to post your reply or Sign up for a free account.