Welcome to Windows Help!
FAQFAQ    SearchSearch      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

Wild Cards

 
   Windows Help (Home) -> Microsoft Access RSS
Next:  Works 9.0 open a word document  
Author Message
Bill

External


Since: Apr 3, 2009
Posts: 9



(Msg. 1) Posted: Tue Jan 19, 2010 9:34 am
Post subject: Wild Cards
Archived from groups: microsoft>public>access (more info?)

I have a case where a distributed 2003 mde file contains
a query that uses the asterisk ("*") character as a wild
card in a criteria expression. E.g., Like "*-*". When an
attempt was made to use that query from within a WORD
2007 mail-merge, an empty set was returned. Having
recalled some discussion long ago about the use of the
percent ("%") character as a wild card, I created another
version of the query and re-distributed the 2003 mde file,
whereby the previously failed WORD 2007 mail-merge
was successful in obtaining the correct set.

Was there some compelling rationale to change the
somewhat de facto standard wild card from the asterisk
to the percent character, or is there more to this than
meets the eye?

Is the asterisk still valid as a wild card with A2007 queries,
or will A2003 queries that use the asterisk fail when a
A2003 mdb is converted to A2007?

The use of the percent character as a wild card in A2003
queries returns an empty set.

Thanks,
Bill

 >> Stay informed about: Wild Cards 
Back to top
Login to vote
Douglas J. Steele

External


Since: Nov 27, 2008
Posts: 61



(Msg. 2) Posted: Tue Jan 19, 2010 1:10 pm
Post subject: Re: Wild Cards
Archived from groups: per prev. post (more info?)

Much as it pains me to say, % is the "de facto wild card" character: Access
uses a non-standard character.

Access 2007 lets you specific ANSI-92 compliancy as an option (Access 2003
did as well). With that set, you must use %. Without it, you should be able
to use *, unless you're working with ADO, in which case you must use %.

 >> Stay informed about: Wild Cards 
Back to top
Login to vote
Bill

External


Since: Apr 3, 2009
Posts: 9



(Msg. 3) Posted: Tue Jan 19, 2010 1:10 pm
Post subject: Re: Wild Cards
Archived from groups: per prev. post (more info?)

Interesting. I can't speak to the history of Access, but
almost every computer language I've used for the past
47 years used the asterisk as the wild card or otherwise
to denote the use of the current memory address.

Thanks Doug, I'll brush up on ANSI-92.

Bill

"Douglas J. Steele" wrote in message

> Much as it pains me to say, % is the "de facto wild card" character:
> Access uses a non-standard character.
>
> Access 2007 lets you specific ANSI-92 compliancy as an option (Access 2003
> did as well). With that set, you must use %. Without it, you should be
> able to use *, unless you're working with ADO, in which case you must use
> %.
>
> --
> Doug Steele, Microsoft Access MVP
> [URL="http://I.Am/DougSteele"]http://I.Am/DougSteele[/URL]
> (no e-mails, please!)
>
> "Bill" wrote in message

>>I have a case where a distributed 2003 mde file contains
>> a query that uses the asterisk ("*") character as a wild
>> card in a criteria expression. E.g., Like "*-*". When an
>> attempt was made to use that query from within a WORD
>> 2007 mail-merge, an empty set was returned. Having
>> recalled some discussion long ago about the use of the
>> percent ("%") character as a wild card, I created another
>> version of the query and re-distributed the 2003 mde file,
>> whereby the previously failed WORD 2007 mail-merge
>> was successful in obtaining the correct set.
>>
>> Was there some compelling rationale to change the
>> somewhat de facto standard wild card from the asterisk
>> to the percent character, or is there more to this than
>> meets the eye?
>>
>> Is the asterisk still valid as a wild card with A2007 queries,
>> or will A2003 queries that use the asterisk fail when a
>> A2003 mdb is converted to A2007?
>>
>> The use of the percent character as a wild card in A2003
>> queries returns an empty set.
>>
>> Thanks,
>> Bill
>>
>
>
 >> Stay informed about: Wild Cards 
Back to top
Login to vote
Douglas J. Steele

External


Since: Nov 27, 2008
Posts: 61



(Msg. 4) Posted: Tue Jan 19, 2010 2:14 pm
Post subject: Re: Wild Cards
Archived from groups: per prev. post (more info?)

Computer language, yes. SQL, no.
 >> Stay informed about: Wild Cards 
Back to top
Login to vote
Bill

External


Since: Apr 3, 2009
Posts: 9



(Msg. 5) Posted: Tue Jan 19, 2010 2:14 pm
Post subject: Re: Wild Cards
Archived from groups: per prev. post (more info?)

Even more interesting. We (IBM) developed SQL and
the VM (Virtual Machine operating system) service
machine that provided the main-frame access to our
relational databases used "*" as the wild card. Somewhere
along the historical development of web-based servers,
something or someone brought about the change?

Bill


"Douglas J. Steele" wrote in message

> Computer language, yes. SQL, no.
>
> --
> Doug Steele, Microsoft Access MVP
> [URL="http://I.Am/DougSteele"]http://I.Am/DougSteele[/URL]
> (no e-mails, please!)
>
> "Bill" wrote in message

>> Interesting. I can't speak to the history of Access, but
>> almost every computer language I've used for the past
>> 47 years used the asterisk as the wild card or otherwise
>> to denote the use of the current memory address.
>>
>> Thanks Doug, I'll brush up on ANSI-92.
>>
>> Bill
>>
>> "Douglas J. Steele" wrote in message
>
>>> Much as it pains me to say, % is the "de facto wild card" character:
>>> Access uses a non-standard character.
>>>
>>> Access 2007 lets you specific ANSI-92 compliancy as an option (Access
>>> 2003 did as well). With that set, you must use %. Without it, you should
>>> be able to use *, unless you're working with ADO, in which case you
>>> must use %.
>>>
>>> --
>>> Doug Steele, Microsoft Access MVP
>>> [URL="http://I.Am/DougSteele"]http://I.Am/DougSteele[/URL]
>>> (no e-mails, please!)
>>>
>>> "Bill" wrote in message
>>
>>>>I have a case where a distributed 2003 mde file contains
>>>> a query that uses the asterisk ("*") character as a wild
>>>> card in a criteria expression. E.g., Like "*-*". When an
>>>> attempt was made to use that query from within a WORD
>>>> 2007 mail-merge, an empty set was returned. Having
>>>> recalled some discussion long ago about the use of the
>>>> percent ("%") character as a wild card, I created another
>>>> version of the query and re-distributed the 2003 mde file,
>>>> whereby the previously failed WORD 2007 mail-merge
>>>> was successful in obtaining the correct set.
>>>>
>>>> Was there some compelling rationale to change the
>>>> somewhat de facto standard wild card from the asterisk
>>>> to the percent character, or is there more to this than
>>>> meets the eye?
>>>>
>>>> Is the asterisk still valid as a wild card with A2007 queries,
>>>> or will A2003 queries that use the asterisk fail when a
>>>> A2003 mdb is converted to A2007?
>>>>
>>>> The use of the percent character as a wild card in A2003
>>>> queries returns an empty set.
>>>>
>>>> Thanks,
>>>> Bill
>>>>
>>>
>>>
>>
>>
>
>
 >> Stay informed about: Wild Cards 
Back to top
Login to vote
Douglas J. Steele

External


Since: Nov 27, 2008
Posts: 61



(Msg. 6) Posted: Tue Jan 19, 2010 3:44 pm
Post subject: Re: Wild Cards
Archived from groups: per prev. post (more info?)

As far as I recall, DB2 (which you also developed) has always used %
 >> Stay informed about: Wild Cards 
Back to top
Login to vote
Display posts from previous:   
Related Topics:
Microsoft Office - Can you update Microsoft office version 2003 to 2007 or do you have to buy the newer version

From access to word - Print - Hello, We open word letter from access with hiperlink code. . . .. . . Application.FollowHyperlink "h:\DRISHOT\" & lettername & ".doc" Is it possible to print the letter instead of open it ? How ? thank you

the setting for this property is too long - Hello. I was running the Access performance option and for some forms and reports there was a message with this: the setting for this property is too long what is this? what should I fix in order to not receive this error. Regards, Marco

Me.Name results in "Invalid procedure call or argument" - I am debugging an Access application written by someone else. In Access 2003 it behaves OK, but the client needs to upgrade to Access 2007 for various reasons. When the app is run in Access 2007 I get a few niggles that I have been working through, but..

converting row into column - I have a table with doctors' information Their addresses are linsted in differnt rows i would like to create a row off addresses with one unique record.
   Windows Help (Home) -> Microsoft Access All times are: Pacific Time (US & Canada)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]