Question on Query table name changing

I have a query that runs against a table "billing". This table is created
monthly by the user as a new table using the Import function. She rename the
previous months "billing" table to "September 2004 billing". Creates a new
table called "billing" and runs a report. When ever she does this if you
look at the query I created to run against the "billing" table it seems to
think it needs to use the "September 2004 billing" table.
--
Thomas

This is a "feature" grrr in Access because stupid people used to go
building lots of stuff, and then change the name of a table, and break their
application.

Now, whenever you rename a table, Access updates the queries that refer to
it.

You could write some VBA code that changes the query back, by using the
Replace function on the SQL property of your QueryDef.

--
Peace & happy computing,

Mike Labosh, MCSD

Feed the children!
Save the whales!
Free the mallocs!

thank you soooooooooooooooooo much - been driving me crazy!!!!!!

"Mike Labosh" wrote:

This is a "feature" grrr in Access because stupid people used to go
building lots of stuff, and then change the name of a table, and break their
application.

Now, whenever you rename a table, Access updates the queries that refer to
it.

You could write some VBA code that changes the query back, by using the
Replace function on the SQL property of your QueryDef.

--
Peace & happy computing,

Mike Labosh, MCSD

Feed the children!
Save the whales!
Free the mallocs!

On Fri, 17 Sep 2004 09:05:06 -0700, Thomas
wrote:

I have a query that runs against a table "billing". This table is created
monthly by the user as a new table using the Import function. She rename the
previous months "billing" table to "September 2004 billing". Creates a new
table called "billing" and runs a report. When ever she does this if you
look at the query I created to run against the "billing" table it seems to
think it needs to use the "September 2004 billing" table.

Two suggestions:

- Simple fix: use Tools... Options... General and uncheck "Track Name
Autocorrect Info".

- MUCH BETTER fix, IMHO: Rather than importing data into separate
tables for each month, have *one single billing table*. Dates *are
data* and should be stored as data, not in a fieldname! Your queries
can and should filter the billing table to extract the data for a
given month.

John W. Vinson[MVP]
Join the online Access Chats
Tuesday 11am EDT - Thursday 3:30pm EDT
http://community.compuserve.com/msdevapps

- Simple fix: use Tools... Options... General and uncheck "Track Name
Autocorrect Info".

WOAH! I thought that had to do with intellisense! That bad boy is getting
unchecked NOW!

- MUCH BETTER fix, IMHO: Rather than importing data into separate
tables for each month, have *one single billing table*. Dates *are
data* and should be stored as data, not in a fieldname! Your queries
can and should filter the billing table to extract the data for a
given month.

Yes. Much better solution. Just pass the month DatePart to a WHERE clause.
--
Peace & happy computing,

Mike Labosh, MCSD

Feed the children!
Save the whales!
Free the mallocs!