Arthur Fuller
fuller.artful at gmail.com
Wed Mar 18 10:45:07 CDT 2009
One thing you might try is to save the union query to a named query and then to use that name in place of the select statement. No promises, but I hate to see a girl wasting all that typing time. If there's anything worse than data entry it's duplicate data entry. Arthur On Wed, Mar 18, 2009 at 11:40 AM, Carolyn Johnson <cjlabs at worldnet.att.net>wrote: > Access2000/2003, Win XP > > I have a combo box with a union query as a row source. There are two > criteria based on data from other fields. The combo box was working great > as of last night. This morning, it will not show the data -- it's showing > no rows. I've made no changes to the database since the last time I put > in > new data using this combo box. > > > The union query itself works fine -- I pasted the sql into a new query and > it shows the correct data. Each half of the union query works fine. > > The combo box works fine with a different backend, but not the one I need > to > use now. > > I did a compact and repair on the "bad" backend -- no change. > > I've deleted the links to the tables and relinked the backend -- no change. > > I've imported all the tables into a new mdb -- no change. > > I've taken the tables from the "working" version that are common to both > and > the specific tables from the "bad" backend and combined them into a new > mdb -- no change. > > I've tried using Access2003 -- no change. > > None of the records in the backend looks screwed up. > > > I'm afraid my only option now is to create a new backend from the version > that works and re-enter all the data. > > Does anyone have any other suggestion? > > > Thanks > Carolyn Johnson > St Louis, MO > >