Daniel,
My work is kind of slow at the moment, so I have more time to contribute.
There's normally many ways to perform similar actions, so if you know the
ultimate goal, it make the choice of methods more rational.
For example the recent poster who insists on running code in edit mode. As
we have no idea what he is trying to achieve, it is not possible to offer
alternatives apart from "No can do".

NickHK

"Daniel Bonallack" wrote in
message ...
Hi Nick

Thanks very much. Looking at some of the other posts today, I notice that
you try to find out what someone is trying to achieve, rather than just
giving them an answer. That's really helpful - I often think I know what
I'm
doing, but then it turns out I'm approaching the problem the wrong way.

Thanks again for your help today.

regards
Daniel

"NickHK" wrote:

Daniel,
This should get you started:

http://www.access-programmers.co.uk/...29ea& t=27242

NickHK

"Daniel Bonallack" wrote in
message ...
OK, thanks. I posted a "what's causing the delay" question to the
forum a
while back, but didn't get an answer. Simply put, if I have Access
open,
the
data extracts faster. If Access is closed, it still works, but
instead of
8
seconds, it can be closer to 90 seconds.

If you have any ideas, I'd love to hear them. And if you know of
simple
code to open Access anyway, I'd still like to learn it, even if that
isn't
my
problem here.
---------------------------- CUT ---------