S
SisterSun
Hello all! I hope you'll be able to help me out with this situation:
My boss is running WinXP Professional, OfficeXP/Access XP(2002); he is
using dbases he created in a2000 1-3 years ago, which, up until recently
seemed to all be working fine.
Several quirks keep popping up within the last month, the most recent of
which is when he tries to create a new query using tables created in
a2000 db in Design View, he selects the fields he wants to appear/sort
(e.g., 5 of 25 fields are selected), but when he RUNS the query, ALL the
table fields are displayed instead of the few he selected.
When he looks at SQL view, Access has used the wildcard to select all
the fields in addition to those he actually asked for.—He can modify the
SQL code, of course, but why should he have to do this?
This unusual behavior occurs (thus far) on all NEW queries he creates
from this dbase in Design View.
Existing queries that he believes he created as recently as April 2004
in Design View run properly.
He says he hasn't ever used the Wizard to create his queries in the
past. When he recreates the same queries against the same tables using
the Wizard (at my suggestion to see how "broken" things were), he gets
what he asked for: e.g., 5 fields of 25 displayed instead of all fields
in the table.
I cannot duplicate the quirk on my system or other assistants systems as
we are running Win2K/Office 2000/a2002, and are not networked for our
applications. (our queries work as requested in Design View or using the
Wizard) What can be causing the problem on my boss's system? Should he
just have the computer technician (whom we are not involving in
troubleshooting because he knows less about how the applications are
designed to run/work than all of us) try to reinstall the application
(after saving/backing up all his existing dbases)?
Your suggestions and feedback are very much needed.
Thanks in advance,
SisterSun
(Avis Patterson, (e-mail address removed))
My boss is running WinXP Professional, OfficeXP/Access XP(2002); he is
using dbases he created in a2000 1-3 years ago, which, up until recently
seemed to all be working fine.
Several quirks keep popping up within the last month, the most recent of
which is when he tries to create a new query using tables created in
a2000 db in Design View, he selects the fields he wants to appear/sort
(e.g., 5 of 25 fields are selected), but when he RUNS the query, ALL the
table fields are displayed instead of the few he selected.
When he looks at SQL view, Access has used the wildcard to select all
the fields in addition to those he actually asked for.—He can modify the
SQL code, of course, but why should he have to do this?
This unusual behavior occurs (thus far) on all NEW queries he creates
from this dbase in Design View.
Existing queries that he believes he created as recently as April 2004
in Design View run properly.
He says he hasn't ever used the Wizard to create his queries in the
past. When he recreates the same queries against the same tables using
the Wizard (at my suggestion to see how "broken" things were), he gets
what he asked for: e.g., 5 fields of 25 displayed instead of all fields
in the table.
I cannot duplicate the quirk on my system or other assistants systems as
we are running Win2K/Office 2000/a2002, and are not networked for our
applications. (our queries work as requested in Design View or using the
Wizard) What can be causing the problem on my boss's system? Should he
just have the computer technician (whom we are not involving in
troubleshooting because he knows less about how the applications are
designed to run/work than all of us) try to reinstall the application
(after saving/backing up all his existing dbases)?
Your suggestions and feedback are very much needed.
Thanks in advance,
SisterSun
(Avis Patterson, (e-mail address removed))