Re: #Name error in Query

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

BBC,

The time to worry is no in early development not down the road where it
could become an issue to fix. Hopefully, in your new psoting you'll get
some feedback that will help determine the issue. My DLookUp's cycle more
records then that and there is no delay, which is why it has me wondering
why yours gives you that 1 to 1.5 second delay.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

"BBC via AccessMonster.com" <u49322@uwe> wrote in message
news:918ebf056ce4c@xxxxxx
There are about 8 records for this table in the test database. It takes
about 1 - 1.5 secs to get the 3 fields (3 DLookUps) and maybe I shouldn't
be
concerned yet, maybe it will be the same with 800 or more recds but I
surely
wouldn't want it to go up anywhere near proportionally. Because I never
did
get the query/SQL way to work I don't have anything to compare to,
although
I've read that DLookUp is faster.
I'm not going to sweat the speed right yet, maybe later though....

I did post the new question in the "Forms" section. The problem seems to
be
very common (large numbers of posts) with the feedback focused on a few
items,
but seems to be a mixed bag of suggestions, most of which I've tried.

thanks again

Gina Whipp wrote:
BBC,

It should not be slow... as a matter of fact, it should be quicker. Does
this database have any data? I'd be willing to take a look.

As for the next question, I would suggest posting a new question... not
because I am not up for the challenge but so everyone can benefit and you
get more prospectives/replies.

Thanks for your advice, I substituted DLookUp and it now works (a little
slow
[quoted text clipped - 31 lines]
Very frustrating, surely can't be that hard ???
Thanks (sorry for the long post)

--
Message posted via http://www.accessmonster.com



.

Relevant Pages