If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Like Converts to ALike in Query
Hello,
Not sure if anyone has seen this but I have a dB that will no longer perform parameter based queries using the LIKE keyword. Instead it changes it to ALike and cannot be saved or run in anything other than ALike. Even if I correct the SQL code to Like it corrupts to ALike. I've created other dB since this first started occurring and all are doing the same thing yet dB created prior to this event still perform a "Like" keyword selection. Is this something unusual or have I missed an M$ upgrade somewhere? Help! |
#2
|
|||
|
|||
Like Converts to ALike in Query
Hi,
Like and ALike difference SHOULD be about the wild card characters you use, the DOS ones, ? and *, or the UNIX ones, _ and % . I *think* it is there to help to explicitly mention what you want to use without having to relay the Options (Tools | Options..."| Tables/Queries, Compatible Syntax ANSI-92 ) when you are outside Access "reach", but still under JET (such as in validation rules definition). See Access 2002 help file under "Examples of field validation rules (MDB)". Hoping it may help, Vanderghast, Access MVP wrote in message ... Hello, Not sure if anyone has seen this but I have a dB that will no longer perform parameter based queries using the LIKE keyword. Instead it changes it to ALike and cannot be saved or run in anything other than ALike. Even if I correct the SQL code to Like it corrupts to ALike. I've created other dB since this first started occurring and all are doing the same thing yet dB created prior to this event still perform a "Like" keyword selection. Is this something unusual or have I missed an M$ upgrade somewhere? Help! |
#3
|
|||
|
|||
Like Converts to ALike in Query
Thank you very much.....that did the trick. I had to
uncheck the SQL Server Compatible Syntax(Ansi92) in the option for the dB. It's rather odd that the switch would have been made without my knowledge but perhaps that's best left for another question. Once again, thank you!!! -----Original Message----- Hi, Like and ALike difference SHOULD be about the wild card characters you use, the DOS ones, ? and *, or the UNIX ones, _ and % . I *think* it is there to help to explicitly mention what you want to use without having to relay the Options (Tools | Options..."| Tables/Queries, Compatible Syntax ANSI-92 ) when you are outside Access "reach", but still under JET (such as in validation rules definition). See Access 2002 help file under "Examples of field validation rules (MDB)". Hoping it may help, Vanderghast, Access MVP wrote in message ... Hello, Not sure if anyone has seen this but I have a dB that will no longer perform parameter based queries using the LIKE keyword. Instead it changes it to ALike and cannot be saved or run in anything other than ALike. Even if I correct the SQL code to Like it corrupts to ALike. I've created other dB since this first started occurring and all are doing the same thing yet dB created prior to this event still perform a "Like" keyword selection. Is this something unusual or have I missed an M$ upgrade somewhere? Help! . |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
query wizard error | Christen | General Discussion | 12 | August 13th, 2004 08:37 PM |
Display Parameter from Form on Report | sara | Setting Up & Running Reports | 10 | July 19th, 2004 04:54 PM |
Hidden files in Ms-Query cause ODBC connect errors or Query is wac | needyourhelp | General Discussion | 4 | July 12th, 2004 09:38 PM |
SELECT function in Query | alexparks | Running & Setting Up Queries | 9 | July 5th, 2004 11:31 AM |
query field reference help | -dch | Running & Setting Up Queries | 4 | June 2nd, 2004 07:30 PM |