Hi all, hoping some of you can shed some light on this. In Access 2007, I put into the table, in a certain field, a certain word field, so I put into design view for that query, in that field, Like "Field" and even though the word field is in that table in that field, it doesn't show it in that particular query? Any ideas how to solve it please?
No results in query criteria
- Thread starter -Chris-
- Start date
- Local time
- Today, 02:37
- Joined
- Jan 23, 2006
- Messages
- 15,526
Chris,
Confused with your post????
Step back and tell readers in real simple English WHAT you are trying to do, NOT HOW you did something. We are looking for WHAT and once we understand that, readers will offer suggestions.options for HOW.
Good luck and welcome.
Confused with your post????
Step back and tell readers in real simple English WHAT you are trying to do, NOT HOW you did something. We are looking for WHAT and once we understand that, readers will offer suggestions.options for HOW.
Good luck and welcome.
You seem very confused dear chap, the post explains it in detail!
MarkK
bit cruncher
- Local time
- Yesterday, 23:37
- Joined
- Mar 17, 2004
- Messages
- 8,436
The best bet, if you are talking about code, SQL or VBA, is post the code. It's just way more precise. Commonly with "LIKE" people get the quotes and/or wildcards wrong, which are a bit finicky. All the more reason to post the code.
Cheers,
Cheers,
Hi Mark, not doing any sql or vba, it's just in the design view of a query in MS Access 2007, putting in the criteria field:
Like "Manor", but it doesn't return any results for that word, even though there's loads of events for that word in that field.
MarkK
bit cruncher
- Local time
- Yesterday, 23:37
- Joined
- Mar 17, 2004
- Messages
- 8,436
A query is SQL. It is code. There is an "SQL View" button on the ribbon, which, if you copy the code into your post, gives your readers tons of very precise info about what you are working on.
Then, if there is a failure, describe the exact symptoms, for instance, "no joy" is not descriptive of a failure mode.
"The problem" will have a precise cause, and using precise language presenting it will increase your chance of success,
Hope this helps,
Then, if there is a failure, describe the exact symptoms, for instance, "no joy" is not descriptive of a failure mode.
"The problem" will have a precise cause, and using precise language presenting it will increase your chance of success,
Hope this helps,
Have been using MS Access since about 2001 and have successfully used many 1,000's of queries over those 14 years, just using the method described above, have never needed to use anything to do with sql or vba. Just setting up the query filters, by simply going into the design view for that particular query, setting the criteria and success every time, so really can't see how it isn't working now? Anyways, here's the code (to preserve confidentiality on certain items, this is different criteria from ones mentioned above, but should still work):
SELECT Table1.[Previous payment], Table1.[Date last checked for payment], Table1.[First name of contact], Table1.[Surname of contact], Table1.[TO which account], Table1.[If part of the deal is them linking to us, which page do they li], Table1.Recurring, Table1.[Still going], Table1.[Changed to three on failures]
FROM Table1
WHERE (((Table1.[If part of the deal is them linking to us, which page do they li]) Like "*TOF*") AND ((Table1.[Still going])="Y"))
ORDER BY Table1.[Date last checked for payment], Table1.[Next payment due];
Any constructive help appreciated.
Chris.
Last edited:
Aaaaargh, just realised, I was inputting the query text into a very similarly worded field! Oooops! With me inputting into the correct field in the query design it all works great. Easily done, and the first mistake in 14 years isn't bad! Thanks to all who gave friendly, constructive help.
One thing, when I went to night school in 2001 to study MS Access, they never touched on sql or vba's simply because it does all I need, without the need to go there, so it begs the question, why is there a need for some to go into the sql or vba? None of my 30+ databases are linked to websites, so do you need the sql coding stuff when it's linked to websites?
One thing, when I went to night school in 2001 to study MS Access, they never touched on sql or vba's simply because it does all I need, without the need to go there, so it begs the question, why is there a need for some to go into the sql or vba? None of my 30+ databases are linked to websites, so do you need the sql coding stuff when it's linked to websites?
Brianwarnock
Retired
- Local time
- Today, 07:37
- Joined
- Jun 2, 2003
- Messages
- 12,701
SQL is what is created by the Design Grid GUI, if your requirements are simple then it can be enough, but even simple multi criteria when some can be not required eg you can select from 1 to n criteria, those not being needed being left as null , this is always driven from a form and done in the design grid is messy, done in SQL is simple and clear.
There are lots of situations that require the use of VBA , you could read through the modules and VBA forum to see some.
Brian
There are lots of situations that require the use of VBA , you could read through the modules and VBA forum to see some.
Brian
Brianwarnock
Retired
- Local time
- Today, 07:37
- Joined
- Jun 2, 2003
- Messages
- 12,701
I suspect that Markk was suggesting that you were not pushing the boundaries of your knowledge and ACCESS's capabilities, but if your requirements are simple why should you.
Brian
Similar threads
