View Single Post
  #9  
Old November 5th, 2009, 11:25 PM posted to microsoft.public.access.forms
jenniferspnc
external usenet poster
 
Posts: 65
Default Is my query at fault for a slow form?

Thaks for the suggestion, it does say 2007 for the file format.

I'm guessing it's related to the network...

"FEleazer via AccessMonster.com" wrote:

You said you are using Access 2007, but is the default file format 2007, or
an earlier version? (Under Access Options, Popular menu.)

I just fixed a problem like this where my form was taking a minute or more to
open over the network. I too, went through all of the tips and tricks for
optimizing, and nothing helped. The database was in Access 2003, but the
default file format was 2000 so that it would be compatible with other users.
I converted all of the databases to version 2003 and the thing just zips
right along now!

Good luck! It took me 4 years to figure this one out!

Fran

Jeff Boyce wrote:
see comments in-in-line below...

Jeff,

[quoted text clipped - 5 lines]
on
each combo box


Unless your PC is a '286, that's not a lot to load...

Your SQL statement uses an "ORDER BY" ... does your tbl_country have an
index on the [Countries] field? Yes, I have an index on Country_ID and
Countries - "Yes, No duplicates."


OK, that rules out slow performance due to a lack of indexing...

I've read but not understood much about removing the RowSource from a
combo
box. How exactly do I do that while still enabling the user to view and
select a country? Would this save time?


While you can remove the RowSource ... , you have to put it back sometime!
Otherwise the combobox doesn't know its source. I don't think this would
matter.

What kind of data type is that field? Country_ID is AutoNumber and
Countries is Text

[quoted text clipped - 4 lines]
network? On a server, but I do have the backend only 2 folders down (the
closest I can get it) and the BE name is shortened.


I've run into horribly slow performance over a network for a variety of
reasons. You might want to check out Tony Towes' website for suggestions on
performance.

Does it appear I've done anything wrong with the combo boxes or the form
design? I didn't realize how much a pain it was to enter an order until I
had to do one. I don't think it's very efficient when one has to wait 10
seconds for each combo box (thank goodness I only have 2 of them).


This kind of performance is not typical.

Here is my query statement with the date limitation removed and a few
other

[quoted text clipped - 6 lines]
FROM tbl_salesorder
ORDER BY tbl_salesorder.Date_Received;


Nothing else comes to mind. Perhaps one of the other newsgroup readers has
experience/can spot something...

Good luck!

Regards

Jeff Boyce
Microsoft Access MVP

Thanks again!!

[quoted text clipped - 142 lines]

.


--
Thanks,
Fran

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...forms/200911/1

.