Search results

Repeating this somehow seems to make you as much as an oaf as dt...

Picking the best event can be tricky sometimes. I may even throw in a DoEvents... I like the Trim(cmbBoxname1 & "") trick and use it sometimes as well...

To start with I would do one local sub proceedure that gets called on each of the combo boxes on change events which enables the other controls if the conditions are true...

This still seems like a bad way to build an end user query tool. So... how would the query param object know what data fld type it is to be used for before you use it?

Cool - I'll have to copy this to my snippets :)

Let us know if it will rip through 400k records in a resonable amount of time - :)

A function seems like a pretty good option to me...

Why not just build a form for the user to put thier params in?

So we don't even know if you were using action queries... In Access, everytime you open a simple select query you always get the latest data. Unlike some apps like Hyperion...

Sometimes you have no choice but to populate intermediate tables you base reports on.

Seems a bit premature when we don't know anymore than we do about his db -

If you don't have a lot of records to traverse you could write a function to calculate it. Or you could simply store in another fld...

Action queries, the kind that can alter data, typically do not run on thier own. Seems you need to find out what in your application is causing them to run.

Question is confusing. Of course you can run a query on command - Probably need more info on what you are trying to do...

You can do this in 2010.

I would try concatenating before the array line...

What you have will work. Another way would be to have a generic specs table. It eould link back to the parts table. This one be a one to one relationship. In this generic table you would have, say 20 flds named something like fld1, fld2, etc.. Then you have another table which would contain spec...

What about Col?

Thats ok, It seems to be working now - Thanks all the same :)

That's exactly what you saw - :confused: