auto complete stops working

[Guest]

Access 2003.

Auto complete was working with a combo box. After adding much functionality
to a database I find that auto complete does not work on any combobox in any
form. So I create a blank database and a simple test shows that auto complete
works. When a form from the faulty database is imported in the test database,
auto complete stops working on the test form. Even if the imported faulty
form is removed, auto complete still does not work.

I tried creating a new database and importing the faulty form after removing
all controls and events from the form except for the combo box. Auto complete
still stops working. Not only on the imported form but also on the existing
form which works prior to the import.

I checked auto expand and it is 'Yes' in all conditions.

What ever is causing the problem on the faulty form seems to cause some
property of the database to change.

Is there some database option or property setting that controls auto complete?

Is is possible that importing a form will cause a database property to change?

 

[Albert D. Kallal]

Hum, something is wrong here...just not sure what....

first, does the combo box sql have the order set? Data kind of needs to be
in order for it really to work....

I would also turn off track-autoname correct (tools->options).

I assume that the base stuff, like the code compiles, and compact/repair has
been done....

I would also disable the "allow autocorrect" in the "other" tab of the combo
box (this is for the spell checker..and you don't want it messing with
stuff).

And, perhaps you turned on ansi92 compatibility?

http://support.microsoft.com/?kbid=824189

 

[Guest]

Thanks for your reply and the solution.

I did turn on the ansi92 compatibility and was not using distinct.

It is remarkable that importing a broken form into a clean database will
break an existing form in the clean db without turning on the ansi92
compatibility.

 

[Guest]

Thanks for your reply and the solution.

Ansi92 was turned on and 'Distinct' was not used in SQL row source.

It is remarkable that importing a broken form into a database where ansi92
compliance was not turned on broke an existing form wihtout turning on
ansi92.

In any case, the issue is resolved. Thanks again.