>I think I may have narrowed it down a little more.
>
> Here is the Row Source for cboFilterLocality
>
> SELECT tblAPCLocality08.ID, tblAPCLocality08.Location,
> tblAPCLocality08.State, tblAPCLocality08.YearCal FROM tblAPCLocality08
> WHERE
> (((tblAPCLocality08.State)=[Forms]![frmAPCSearch]![cboFilterState]) AND
> ((tblAPCLocality08.YearCal)=[Forms]![frmAPCSearch]![cboFilterYear])) ORDER
> BY
> tblAPCLocality08.Location;
>
> However I know think that a piece of code in the on change event in
> cboFilterState is causing it. When I blocked the code out everthing ran
> fine.
> The code is
>
> Private Sub cboFilterState_Change()
> 'Me.Refresh
> 'DoCmd.Requery
> End Sub
>
> I need this code or something similar so that when someone changes the
> state
> and year the locality list will change to match the new selections.
>
> Is there a better way to code this that won't slow the form down so much?
>
>
>
>
>
> "BruceM" wrote:
>
>> This link describes how to use cascading combo boxes:
>>
http://www.databasedev.co.uk/filter_combo_boxes.html>>
>> Here is another one:
>>
http://www.mvps.org/access/forms/frm0028.htm>>
>> It seems you are using Year as a field name. "Year" is a reserved word,
>> so
>> that could be a problem, but I don't know if it would affect performance.
>>
>> What is the Row Source of cboFilterYear, and what is the bound column?
>> Do
>> you get better results if you change the criteria for the Year field to a
>> number such as 2008 rather than a reference to cboFilterYear?
>>
>> "pfm721" <pfm721[ at ]discussions.microsoft.com> wrote in message
>> news:064B29E3-4D08-4E23-9440-36DA4C6CA17D[ at ]microsoft.com...
>> >I just modified the query that cboLocalityFilter was based on. Before
>> >the
>> > query had
>> >
>> > Locality
>> > State - Forms!frmAPCSearch!cboFilterState
>> > Year
>> >
>> > Now it has
>> > Locality
>> > State - Forms!frmAPCSearch!cboFilterState
>> > Year - Forms!frmAPCSearch!cboFilterYear
>> >
>> > When it was just the state it ran fine with almost no noticeable delay.
>> > When
>> > I added the Year it slowed considerably.
>> >
>> > "BruceM" wrote:
>> >
>> >> How are you limiting by year? That is, how are you changing or
>> >> setting
>> >> the
>> >> cboFilterLocality Row Source based on year?
>> >>
>> >> "pfm721" <pfm721[ at ]discussions.microsoft.com> wrote in message
>> >> news:A2467F8C-02EA-477A-85E2-8D3F7EFB9FCA[ at ]microsoft.com...
>> >> > One more thing I forgot to mention is that it was much quicker
>> >> > before I
>> >> > had
>> >> > it limit by year. When it was just limiting by state there was
>> >> > almost
>> >> > no
>> >> > delay.
>> >> >
>> >> > "pfm721" wrote:
>> >> >
>> >> >> I have been updating a database that I did not design but have been
>> >> >> tasked
>> >> >> with updating. We need to add a new year of prices to the database.
>> >> >> I
>> >> >> have
>> >> >> all of the new info in already and it works fine. However the way
>> >> >> that
>> >> >> I
>> >> >> changed the form has slowed it down significantly.
>> >> >>
>> >> >> The form has several cascading combos and the last one is slowing
>> >> >> the
>> >> >> form
>> >> >> down.
>> >> >>
>> >> >> cboFilterState
>> >> >> cboFilterYear
>> >> >> cboFilterLocality
>> >> >>
>> >> >> the last combo is the one with the problem it is based off of the
>> >> >> information in
>> >> >> tblLocality
>> >> >> ID - Auto
>> >> >> State - text
>> >> >> Location - text
>> >> >> Year - Number
>> >> >>
>> >> >> The data in the combo is based on a query which narrows down
>> >> >> location
>> >> >> by
>> >> >> the
>> >> >> year and state selected in the first two combos. It is taking 15-20
>> >> >> seconds
>> >> >> for the box to populate. Is there something that I can do to speed
>> >> >> this
>> >> >> process up?
>> >> >>
>> >> >>
>> >>
>> >>
>>
>>