"Save as" default file name in Access 2007

[rweav]

When using "Save as" with existing queries this version uses a defalult file
name "Copy of existing file name". In earlier versions it used the existing
filename. I know this seems petty but I have a couple of databases I use to
modify data in our system where I start from an existing query and make
changes and then keep the modified query as a tracking system. I include our
claim number in the file name so now I have to first select and delete "Copy
of " from the filename before replacing the claim number. I do this daily and
it seems so unnecessary. Is there a way to change the default filename when
using "Save as" back to the existing filename with no prefix added by the
program?

I have searched this forum and others before posting here and would
appreciate any help.

Thanks,

Rick

 

[Douglas J. Steele]

I don't understand why you're creating multiple copies of the same query!

Can't you just use a parameter query and specify the claim number you want?

 

[rweav]

I am opening an existing query, replacing a source table and in many cases
changing multiple parameters. The target tables to be updated stay the same.
I save the query with the new parameters as a means of tracking changes for
audit purposes. The data involves payments made on self-insured workers
compensation claims and the auditors and actuaries sometimes request historic
information and keeping these queries has saved me on a number of occasions.

I just can't grasp why this had to change. In all other office applications
when you choose to "Save as" the filename stays the same allowing you to add
a prefix or suffix to distinguish the changes.

It's obviously workable as is but I would love to eliminate that extra step
of highlighting and deleting "Copy of" from the file name.

Thanks

 

[Douglas J. Steele]

Sorry if I come across rudely, but perhaps the problem is how you're using
Access. It sounds as though you've got multiple tables, one for each worker
or one for each company, or something like that. That's a mistake. I really
can't think of a legitimate reason to be saving queries in the manner in
which you describe.

 

[boblarson]

I have to agree with Doug on this. It sounds like you are trying to do
things in Access which

1. will cause you more work than is necessary

2. are not taking advantage of a relational database

So I think more information about your design is required for us to give you
good advice on what to do. We tend to make sure to teach as opposed to just
doing "band-aid fixes" and I think you want a "band-aid fix" when you need
some additional help.

 

[rweav]

I am using Access to interface with the SQL database used by my company's
Claims Processing application. I have been developing queries to perform some
functions not provided by the application such as moving a payment that was
paid on the wrong claim to the correct claim or changing the type of payment
after it has been printed. I appreciate the input but I do not have the SQL
skills to perform these tasks and must continue to use Access.

It would just help me to be able to modify this default file name setting.

As I said before, I can continue deleting "Copy of" every time I save a
modified query. I just thought maybe someone knew an option or registry tweak
for this that I have not been able to find.

Thanks.

 

[a a r o n _ k e m p f]

your life would be much easier if you were using SQL Server

then you could use DDL statements in order to 'copy' the query as many
times as you would like.
Of course, Jet doesn't really support DDL (because it is a database
engine without a future).

Maybe you should learn how to write SQL; it's just design view-- in
SQL Server, you can _SEE_ SQL view and design view at the same time--
So sorry that Jet doesn't have this _VERY_ helpful feature (to help
you to learn SQL)

 

[Douglas J. Steele]

Of course, Jet doesn't really support DDL (because it is a database
engine without a future).

Of course, Jet does support DDL.

 

[rweav]

Thanks for the suggestions. I'll just have to put up with this inconvenience.
I am very happy with Access as my SQL tool and would rather not re-invent the
wheel when it's meeting my company's needs so well.

I'll consider this thread closed regarding the original question.

Thanks again,

Rick