Update query ---doesn't

  • Thread starter Thread starter Mike Painter
  • Start date Start date
M

Mike Painter

I brought a copy of an application home, modified an update query to update
two additional fields (don't ask).
It worked.
I took just the query back and copied it to the original program.
It does not work.
Any ideas?
 
It does not work.
You really explained it well! You did not bother wasting time stating the
obvious stuff like error messages, how the results were not what was
expected, and examples of input, output, and what should have been the output.
 
Did you delete the old copy of the query before copying it to the other mdb?
If you do an import of an object that already exists, it does not overwrite
the exiting object with the same name. It appends a number to the name and
adds it to the object collection. For example, if Home.mdb and Work.mdb both
have a query name MyQuery and you open Work.mdb and import MyQuery from
Home.mdb, you now have:
MyQuery
MuQuery1
 
KARL DEWEY wrote:

Well, lets see, thre were no error messages.
The "input" would have been the results of a calculation and the "output"
would also have been the results of that calculation in both cases.
31.25 - 2.5 = 20.00 and 2.5 were the results on one machine, 0 and 0 were
the results on the other machine. The "output", by which I assume you mean
ther results of the query should have been 20.00 and 2.5
Does that help?
 
I renamed the old one before making the transfer. I wrote this application
more than ten years ago so am familar with that experience.
 
Mike said:
KARL DEWEY wrote:

Well, lets see, thre were no error messages.
The "input" would have been the results of a calculation and the
"output" would also have been the results of that calculation in both
cases. 31.25 - 2.5 = 20.00 and 2.5 were the results on one machine, 0 and
0
were the results on the other machine. The "output", by which I
assume you mean ther results of the query should have been 20.00 and
2.5 Does that help?

Still a pretty poor explanation. Were the values being updated zero to
start with and they simply were not updated or were they updated TO zero?
In other words the problem could be that the SELECT part of the query is not
providing correct results or the problem could be that the update is simply
not happening which would generally indicate a criteria problem.
 
Rick said:
Still a pretty poor explanation. Were the values being updated zero
to start with and they simply were not updated or were they updated
TO zero? In other words the problem could be that the SELECT part of
the query is not providing correct results or the problem could be
that the update is simply not happening which would generally
indicate a criteria problem.

They start as zeros and get updated with non zero numbers in the query on my
machine at home.
Same query, same tables, same records, same values in the working version,
no updates occur.
This query is the same on both machines. I copied the query from one machine
to a thumb drive aand then to the working machine, have compared them
visually.
They work on one machine and not on the other.
 
Jan Baird is out of the country until September 20. Every effort will be
made to respond to messages, but please be patient.
 
Jan Baird is out of the country until September 20. Every effort will be
made to respond to messages, but please be patient.
 
Jan Baird is out of the country until September 20. Every effort will be
made to respond to messages, but please be patient.
 
Back
Top