By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,190 Members | 1,063 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,190 IT Pros & Developers. It's quick & easy.

Why delete query won't run?

P: n/a
MLH
SQL String #1
DELETE * FROM tblPreliminaryVINs Where PVIN In (Select SerialNum From
tblVehicleJobs);

SQL String #2
DELETE tblPreliminaryVINs.*
FROM tblPreliminaryVINs INNER JOIN tblVehicleJobs ON
tblPreliminaryVINs.PVIN = tblVehicleJobs.SerialNum;
String #1 fails. String #2 runs. Anyone know why #1 doesn't work?
Nov 28 '06 #1
Share this Question
Share on Google+
5 Replies


P: n/a
"MLH" <CR**@NorthState.netwrote in message
news:7e********************************@4ax.com...
SQL String #1
DELETE * FROM tblPreliminaryVINs Where PVIN In (Select SerialNum From
tblVehicleJobs);

SQL String #2
DELETE tblPreliminaryVINs.*
FROM tblPreliminaryVINs INNER JOIN tblVehicleJobs ON
tblPreliminaryVINs.PVIN = tblVehicleJobs.SerialNum;
String #1 fails. String #2 runs. Anyone know why #1 doesn't work?
Because the first one is not an updatable recordset?

Keith.
Nov 28 '06 #2

P: n/a

MLH wrote:
SQL String #1
DELETE * FROM tblPreliminaryVINs Where PVIN In (Select SerialNum From
tblVehicleJobs);

SQL String #2
DELETE tblPreliminaryVINs.*
FROM tblPreliminaryVINs INNER JOIN tblVehicleJobs ON
tblPreliminaryVINs.PVIN = tblVehicleJobs.SerialNum;
String #1 fails.
I dunno, it works for me....

Nov 28 '06 #3

P: n/a
MLH wrote:
String #1 fails. String #2 runs. Anyone know why #1 doesn't work?
It works for me, hon. What error message are you getting?

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200611/1

Nov 28 '06 #4

P: n/a
MLH
Forgive me for putting this off. I just discovered I'm
dealing with a corrupted database file. Therefore,
any unusual behavior might well be attributed to
the corrupt file. Pardon me while I back up 'n punt.

The latest perversion of my database occurs when
I press CTRL-H in a field of an open table. After half
a dozen or so replacements, Access97 is immediately
closed. It does not crash 'n hang. It just disappears
from the screen and the task manager.

Testing other database files on the same machine,
the behaviour of CTRL-H is quite normal. I've compacted
and repaired the database and backed it up several
times for added safety. But the anomoly persists. Knowing
of this corruption, its pointless to consider other anomolies
because at this point my database is completely untrustworthy.
Nov 30 '06 #5

P: n/a
MLH wrote:
Knowing
of this corruption, its pointless to consider other anomolies
because at this point my database is completely untrustworthy.
Yes, you either need to restore from a backup from before the curruption (I
hope the corruption is very recent so you have oa good backup!) or you'll
have to rebuild it starting with a brand new database container. Good luck
to you on that.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200612/1

Dec 1 '06 #6

This discussion thread is closed

Replies have been disabled for this discussion.