Remove Enter Parameter Value

Infinite

More left to learn.
Local time
Yesterday, 21:56
Joined
Mar 16, 2015
Messages
402
Hello :) I have been trying, no matter what I, I can not remove the Enter Parameter Value. In the attached date base, go to frmEvents, and double click on one of the shows, and you will get that error. I have deleted lines of code, text boxes, and anything else that is associated with the txtSearchS.
I would be VERY happy if some one could tell my it is doing that, and why it is not after removing everything I could think of that goes with that. Thanks!
 
Last edited:
frmEventsEdit is based on SQL (a query) that refers to a textbox that doesn't exist:

Like [Forms]![frmEvents]![txtSearchS] & "*"
 
err....There is a text box named txtSearchS

Its on the form frmEvents
its the text box you search in for shows in...
 
Err, perhaps you're thinking of frmItems, which does have a search textbox on it. frmEvents does not, unless it's very well hidden. ;)
 
Ok, here is a image of it.
 
Last edited:
oh.....Never mind, give me a minute, wrong data base :P
 
Ok, :o Here is the correct one, and NOW you can see in the frmEvents there is now the correct txtSearchS
 
Last edited:
First thing your macro does is close frmEvents, so it's not available to frmEventsEdit.
 
Ah, so closing the form was not the smartest thing I could have done :)
Should I just never close the frmEvents? Because I get the same thing when I close and use frmItems.
 
Well, you certainly can't close it if a subsequent form/process expects it. I haven't followed your whole process, but an alternative would be to copy the search value to a hidden textbox on a form that does stay open, or perhaps use TempVars, which would be accessible to the query. I haven't used TempVars myself, but I'm old fashioned...or just old. :p
 
Well, I googled tempvars but it would be removed after I close the data base. I need to (like you said) create a form that just stays open in the backround...maybe a form that has its size set to 0,0,0,0? Im going to try that. Ill tell you if it works. Thanks!
 
Well, That wont work. Gonna have to think of another way to do that...
 
If you want a value to survive closing the cb, neither would work. Are you sure that's required?
 
Required? No, but that pop up will drive me (and any one who uses it) Krazy. Wish there was a way to remove errors or popups like that. Well, I could just make it so there is no way to close frmEvents...Something like that would work.
 
Not sure what you mean by "Wish there was a way to remove errors or popups like that". There is, you either leave the first form open while the second form is open, or find some other way of getting the parameter to the query. Simplest for you is probably taking the close action out of the macro, and close that form from the close event of the second form. I don't know the overall flow of your app, so I can only through out general thoughts.
 
Yep, but I thought of a better way, and, instead of close, I just have it minimize. A lot easier, and less hassle.
 
Glad you got it sorted. I'd have probably hidden it, but either should work.
 
Last edited:
I've have probably hidden it, but either should work.

You mean "I'd" not "I've" ?

And, how would have you done that?
 

Users who are viewing this thread

Back
Top Bottom