Sounds to me like an XY-problem, and I would strongly suggest looking into the following two alternatives to the solution you're aiming for:
- If those values (30, 35, 36, and 40) have a shared meaning, consider normalizing them in a table in your database, and having the value for
SecurityDrops correspond to that group of values (e.g. through the foreign key).
- Use a magic value such as "-1" and have the query define an exception for that situation.
- Use a magic value such as "-1" for
SecurityDrops, and if it is selected have another parameter pop up for SecurityDropValues that is MultiValued and allows the user to input 30, 35, 26, and 40.
If you insist on the direction you suggest in the question, the "solution" would be to make the parameter of type text, and allow the user to input comma-seperated values. You'll have to parse the input for the parameter in the SQL then though, which isn't pretty.