A few months ago, I posted a message about an Apply Filter error
message that only appeared on 2 of 20 or so computers using a program
I developed. None of you had any suggestions although Marco tried to
help.

I finally go my hands on one of those computers and quickly determined
that the problem was the use of Requery. I changed that to RunCommand/
Refresh and the macro ran perfectly.

So, my question: Should I change all the Requery commands to
RunCommand/Refresh?

Nance

Tomahawk Lady wrote:
I went to Google and searched for
access refresh vs requery
and there's enough hits to fill you in.

As to answering your question, my feeling is don't fix what isn't broken.

Regarding your previous post...not everyone has gotten the error you
have received. I never have. One has to hope others have experienced
something similar.

Sometimes it helps if you produced the code to let others review. For
example, copy/paste all the code events for the textboxes that were
creating the error; Textbox1 and Textbox2. You can also convert a macro
to VB as well. Seeing the code will help oftentimes. Look for "Convert
Macros To Visual Basic" in Access help. I doubt it makes a difference
but who knows, you might have set AllowFilter to false under the form's
data tab in properties inadventently. Or the combobox's recordsource
get's filter isn't getting updated. I would think its probably in your
form's or textboxes update or OnCurrent events that's causing the issue.
That's my throw mud at the wall at hope something sticks answer.

Tomahawk Lady <nancycmarshall (AT) verizon (DOT) net> wrote in
news:1945108f-d7d5-41d8-85f9-b491631f1d1c (AT) s9g2000yqa (DOT) googlegroups.com
:

Most of us with extensive Access experience don't use macros. And I
don't use DoCmd.RunCommand for anything that has a direct VBA
command.

In short, my bet is that the problem is related to the way macros
interact with the UI, and that if you were doing it all in VBA, you
wouldn't have the problem. That would explain why nobody has
experienced the problem, since most of the people offering help in
the Access newsgroups graduated from using macros a long time ago.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

David W. Fenton wrote:

On 4/17/10 2:18 PM, Salad wrote:
I dunno.

For starters, macro designer was completely revamped in 2010. It
functions almost like writing code but with much more stronger
intellisense so it actually requires less keystrokes to write macros
than the equivalent VBA code to do something.

Once you become familiar with list of macros (which isn't too hard to
do) it's quite easy to pick up on it. The "macro gurus" will have to
learn the new designer as well and possibly may have un-learning to do
as the new macro designer also introduces If/Then, SubMacros and error
handling.

In my case, I ran away from macros after I managed to corrupt a database
after deleting a macro when I was a noob fumbling the way around Access.
For all I know, the corruption may have been my fault, but I remember
that I couldn't actually delete macro - it wouldn't go away so I went
and learned VBA and never looked back.

Now with 2010, I can see some use in using macros for simple tasks and
for data macros & web databases (where there's no choice anyway) and I'm
quite glad they enhanced the macro language - it's not full bodied as
VBA and I will continue to write more VBA than macros but it's
improvement nonetheless.

On 4/17/10 6:59 AM, Tomahawk Lady wrote:
With knowing a bit more, I'll have to answer in general terms.

Refresh and Requery are quite distinct and should be used appropriately.
I use Refresh when I want to check for any values that may have changed.
I use Requery when I want to check for any new records that may have
been added and rows that may have been removed. Refresh is cheaper than
Requery.

Requery has a side effect of changing the form's record selector back to
the first record - it's as if you close & re-open the form and lost the
place. Refresh doesn't do that but you won't be able to tell if someone
else added a new record or not you can only be sure you have the latest
values for records you already can see.

They are different for a reason and thus should be used accordingly.

Salad <salad (AT) oilandvinegar (DOT) com> wrote in
news:vpedncb9UbIzuFfWnZ2dnUVZ_g6snZ2d (AT) earthlink (DOT) com:

Not so much, seems to me, since the macros are pretty much
completely different, and their utility comes entirely from the
massive enhancements to macros that were not present in previous
versions of Access.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

Banana <Banana (AT) Republic (DOT) com> wrote in
news:4BCA348B.4070507 (AT) Republic (DOT) com:

My concern with macros, even in their new guise, is managing them.
In VBA you can easily tell what's in use and what's not, because
it's compiled. That is, you can rename a function/sub, hit the
compile button and immediately know if it's redundant code that can
be removed. With macros, you can't do that.

Secondly, unless I haven't heard about it, there's no way to browse
through and search all macros and see what's interconnected.
Embedded macros were introduced in A2007 and they make it even
harder, in my opinion, to tell where things are happening.

So, troubleshooting seems to me like it would be very difficult.
Also, the main way I make my living is taking over old apps that
need revival, and very often this means figuring out a tangle of
spaghetti macros and rationalizing it into something more
manageable. If there has been no improvement in the tools for
maintaining and auditing macros, I, too, will avoid them for
anything where they are not essential (just like I do already).

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

Banana, As I played around, I seemed to discover that Refresh only
works with bound objects, while Requery works with unbound. Is that
correct? Nance

Tomahawk Lady <nancycmarshall (AT) verizon (DOT) net> wrote in
news:710b673e-810b-4680-aaff-b8c37b3b1b8f (AT) x12g2000yqx (DOT) googlegroups.co
m:

Have you read the help file on the two?

Refresh goes back to the database and checks to see if there have
been any changes to the currently displayed data and REFRESHES it.

Requery completely reloads the data set from scratch, which will
eliminate any deletions and pick up any new records. It will also,
incidentally, show any updates to any of the other records.

It's really not a confusing distinction if you just bother to try to
understand it.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/