Re: Warn me Not
- From: "Allen Browne" <AllenBrowne@xxxxxxxxxxxxxx>
- Date: Sat, 1 Sep 2007 10:05:31 +0800
Use Dir() to test if the target file exists.
If so, Kill it before executing your query.
--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Michael Conroy" <MichaelConroy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:27B00403-F062-458E-98F2-1733A282910F@xxxxxxxxxxxxxxxx
First, I would like to say I have the setwarnings to false on the line before
the code and I am still getting a warning. It is kind of an unusual
situation. I am taking a table in one database and, using a make table query,
putting a copy, with a new name into the backup database. The SQL to do this
is working and is not in question. However, if there is a file with the same
name, (tbl August 2007) already in the backup db, I get a run time error
3010, table 'tbl August 2007' already exists. Since the error message is
generated by the other database I went in there and unchecked the Action
Queries, but I discovered that this change works for all of Access, not just
the one database so I had to turn it back on. And Action Queries and Document
Deletions did not seem to eliminate the warning. Do you have to restart
Access when these options are changed? I did not.
I have learned with Access that if I run into a wall, the wall is there for
a good reason and maybe I have to find another way to accomplish my task. So
if you have a way to turn this warning off great, however, I will gladly
accept another way to accomplish my task. I can make the table with the new
name in the current database, how then can I move or (copy/delete) it to
another database? As always, any help is greatly appreciated.
--
Michael Conroy
Stamford, CT
.
- Prev by Date: Recursive(?) Query
- Next by Date: Re: Warn me Not
- Previous by thread: Recursive(?) Query
- Next by thread: Re: Warn me Not
- Index(es):
Relevant Pages
|
Loading
