record source explicitly says populate etc and not the actual SQL
record source explicitly says populate etc and not the actual SQL
I'll have to admit you have me stumped. Any chance you could post your db; removing any sensitive data of course?
i don't have a problem with that, but I can't see an obvious way of doing it.
thanks
Do a Compact and Repair, Zip up the db, then go to Advanced when posting and scroll down a bit.
zip attached. thanks
You had DataEntry set to YES. That will only show NEW records.
hi
that makes sense. however, i've set that to No, but my onClick still returns no records. i've tried just having me.requery, docmd.requery, me.refresh, but the detail section won't populate, and still get 0 records returned.
thanks
Change the name of your 3 controls to match the query "Forms!..." entries. I forgot I had changed them.
thanks. so is it just me.requery for OnClick? this does not work but....i've just double-clicked the query in the left hand pane and I get a datasheet with the correct record returned???????
How about this one? I have to leave for several hours. I'll check back later.
Shouldn't they be bound to the query or sql statement you posted and not the table?they're all bound controls based on the only table I'm using
Sorry, ignore. I was working off of an out of date page.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.
Okay, here’s what I changed.
- Turned off Data Entry
- Changed the query references to the actual names of the three controls
- Changed the button code to just Me.Requery
- Turned on Navigation buttons so I could see what’s happening
- Saved the query to a name using CamelFontName without spaces
- Pointed the form to the new query
MS Access tries to help sometimes. As a result, if it can’t find a control with a particular name, it looks for a field with that name. It is why I and many developers change the name of our controls so it does not match the name of the bound field. MS Access defaults to naming a bound control the same as the field to which it is bound. This can cause unintended consequences and confusion.
Names with embedded spaces in them can on occasion be problematic. It is why I use CamelFontNames but you can use the under_score if you prefer. Try and avoid names with embedded spaces.
thanks RuralGuy. took out the spaces in the query name etc and away I went. Thank you very much for your invaluable help
Excellent! Very glad we could help.