Wildard in Query fed from a search form

G’day Galaxiom.

Did you notify Microsoft of that error? I didn’t simply because I didn’t think they would do anything about it.

Certainly amazes me how many other sites will copy and paste something from another site, including a Microsoft site, without even thinking about it.

It demonstrates to me just how much some other people on the www pretend to know. (Or not know.)

Astonishing ignorance…

Chris.
 
Did you notify Microsoft of that error?

No, but I assumed someone already had but was ignored.

I didn’t simply because I didn’t think they would do anything about it.

You would be right there. I did tell them about this blatently obvious one and nothing changed. Wrong on two counts. I expect they simply pasted the content from the Enabled property and changed the term to Locked.

"The default setting of the Locked property is True. This setting allows editing, adding, and deleting data."

Certainly amazes me how many other sites will copy and paste something from another site, including a Microsoft site, without even thinking about it.

Then, having repeated the same error word for word, they add their own copyright notice!

It demonstrates to me just how much some other people on the www pretend to know. (Or not know.)

Astonishing ignorance…

No better demonstrated than on the thread where you went to great lengths to explain why it was wrong.
 
Nz() actually returns the special Variant value Empty
I am suitably humbled:o - but the effect is as described
 
CJ.

It is not about being suitably humbled it’s about being better informed.

Even though the ‘effect is as described’ might be correct under this circumstance it is not the same thing. People who suggest that a Function can somehow ‘flip a coin internally’ to decide what data type can be returned simply do not understand what is going on. A Function has to return a value based on the information supplied to it.

It brings into question if the person actually knows what it means by a Function returning a value. That is a very basic point in VBA and people do not like being told that they are wrong on such a basic point.

Some people will go to great lengths to protect their ignorance by trying to muddy the waters. But what they are actually doing is reducing the possibility of others trying to learn the basics. That should not be what this site is about.

So what I suggest to all is this:
IF IN DOUBT, ASK.
It is totally inappropriate to try and argue the point as was done by JBB in that other thread.

Chris.
 
I have built a search form to feed information to a query. The form uses combo boxes tied to table values, and all have wild cards built into them so if the user leaves the combo box they get all the records. I also have to text boxes representing start date and end date. I would like to allow the user to leave these blank and get all there as well. I have been looking through my one Access book, as well as searched all over the internet, but I cant seem to find the way to do this.

My filter criteria for the text based combo boxes are like this:
Code:
Like "*" & [Forms]![ReportDesignF]![Company] & "*"
My filter criteria for the Start and End Dates looks like this:
Code:
Between [Forms]![ReportDesignF]![StartDate] And [Forms]![ReportDesignF]![EndDate]+#11:59:59 PM#
In this case of the user leaves the date values blank, the query returns nothing. I would like to return all dates if that is the case. I am assuming it is my lack of knowledge of wild cards and how they work with date values.

DeanFran,

This is an interesting post however the most important question at the moment is to enquire as to weather or not you now have a working solution.

I think I can create one for you but it will take some time.
 
Yes CJ London's eloquent suggestion did the trick. The search form has a label that prompts the user to use mm/dd/yy format or to use the date picker tool. That said, Access is smart enough to handle most ways folks might enter the date values.
 
Access is smart enough to handle most ways folks might enter the date values.

No matter how smart, Access cannot possibly tell what is required in an ambiguous date such as 3/4/2014.

It uses the Regional date format.

When confronted by a date that is not valid in the Regional date format it will quietly interpret it as another. To me, accepting a mistyped date because it fits a different date system isn't smart at all.
 

Users who are viewing this thread

Back
Top Bottom