R
Ryan
I have a database that has been working fine in development in access 2003.
I have a simple Union query that works great, but when I open the program in
access 2007 I cant even see the Union queries. Here is a simple example of
one of my Union queries.
select * from 05qryPhysician
UNION ALL Select * From 05qryPhysicianTotals;
Even though the Union query is not visible, I have a command that exports
the data from access to excell that kinda works. Here is what I get when I
run the command.
The name, 05PhysicianTotals, either conflicts with a
valid range reference or is invalid for Excel. The name has been
replaced with _1_05PhysicianTotals.
What am I doing wrong. Why cant I edit or even view my Union Queries in
Access 2007? Why is it wanting to rename then when I run my command?
You may still need to manually update any references to this name used
in VBA code or as text arguments in functions. You must close and
reopen the workbook before these changes take effect.
I have a simple Union query that works great, but when I open the program in
access 2007 I cant even see the Union queries. Here is a simple example of
one of my Union queries.
select * from 05qryPhysician
UNION ALL Select * From 05qryPhysicianTotals;
Even though the Union query is not visible, I have a command that exports
the data from access to excell that kinda works. Here is what I get when I
run the command.
The name, 05PhysicianTotals, either conflicts with a
valid range reference or is invalid for Excel. The name has been
replaced with _1_05PhysicianTotals.
What am I doing wrong. Why cant I edit or even view my Union Queries in
Access 2007? Why is it wanting to rename then when I run my command?
You may still need to manually update any references to this name used
in VBA code or as text arguments in functions. You must close and
reopen the workbook before these changes take effect.