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

A97 error "Operation Must Use An Updateable Query" ???

P: n/a
MLH
What is the meaning of this error?

Operation Must Use An Updateable Query

???
Nov 13 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Usually it means you can't update a table from a query that is itself
not updateable - as is the case with most queries involving tables with
one-to-many relationships etc.

The trick is to have it as an append query, writing the values to a
seperate temporary table and then run another query to update the
values from this to the table you were trying to update in the first
place. Pain in the @rse but the only workaround i know of.

....of course this might not be the problem: more details please :)

Nov 13 '05 #2

P: n/a
MLH
Actually, you may have shed meaningful light on the issue for me. I'll
have to study about it some more. Any idea why the problem might
show up on an A97 runtime app installed on a Win98 box and NOT
on an XP box? Believe me, tested 'n verified. Brand new install does
not result in err launching on XP, but opposite is true on a 98-box.

xxxxxxxxxxxxxxxxxxxxxxxxxxx

Usually it means you can't update a table from a query that is itself
not updateable - as is the case with most queries involving tables with
one-to-many relationships etc.

The trick is to have it as an append query, writing the values to a
seperate temporary table and then run another query to update the
values from this to the table you were trying to update in the first
place. Pain in the @rse but the only workaround i know of.

...of course this might not be the problem: more details please :)


Nov 13 '05 #3

P: n/a
MLH
I must apologize. Somehow, the installation of the A97 runtime
app onto a Win98 box resulted in the mde file being read-only.
Attrib MyFile.mde returned +R. After changing it, the problem
went away. I need to post another topic asking "Why would
A97 runtime installation create the target mde file with +R
(read only) file attribute setting on a Win98 box?" I think I'll
ask that of the group.
Nov 13 '05 #4

P: n/a
Probably a dll problem. De-compile it, install it and then re-compile
on the target machine... that should circumvent vbe6.dll errors anyway,
but it's hard to know - access doesnt move from platform to platform
very happily. different versions of jet, odbc, vb environment etc tend
to conflict with one another. sorry i cant be of more help

Nov 13 '05 #5

P: n/a
MLH
That's quite alright. Thx for the comments. Its easy enough, the work
around. Just change the file attribute on the target machine once
installed. Only necessary once.

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Probably a dll problem. De-compile it, install it and then re-compile
on the target machine... that should circumvent vbe6.dll errors anyway,
but it's hard to know - access doesnt move from platform to platform
very happily. different versions of jet, odbc, vb environment etc tend
to conflict with one another. sorry i cant be of more help


Nov 13 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.