Update query does not work in Macro -- but runs correctly when run by itself

[Pack10]

I have a macro which contains a few update queries (8). My manager tells me a specific record was not updated
with the appropriate value, and when I reviewed the table, it was not updated.
Now, when I run the query from the Navigation pane, it updates the record correctly.
Do I need to do something in my macro or something....this is strange.

 

[lameid]

The only thing that comes to mind is that the record was locked when the macro was run and you set warnings to false / no in the macro and therefore did not see the error.

 

[Pack10]

Others have had this, I see it in Google...but not clear on the fix. I am running them from a module now...and
have broken them up into 4 subs.....I will let you know.

 

[Pack10]

This is so strange. When I run the update queries via code DoCmd.Openquery it's not updating all records...if i run it manually, it updates
all records. WHat is going on...is there a cache issue.

 

[dhookom]

Pack10,
Are you ignoring lameid's comment?

Duane
Hook'D on Access
MS Access MVP

 

[lameid]

A thought, is it the parameter bug?

http://allenbrowne.com/bug-13.html

 

[Pack10]

There are no parameters. The table contains
37,000 records,there are 16 queries
Most are update types. I do see a message
That there is not enough disk space
To undo the operation with a yes no
Cancel. If I suppress messages this
Won't be seen, does that have something
To so with my issue. I am going to try
Running two queries in 8 macros.
See if they run that way.

 

[lameid]

I'd try running the one query in a macro.... and then add things until it does not work starting with Set Warnings and then queries....

 

[Pack10]

Latest update. I have broken up the queries, I am running about 4 to a Macro and it appears to be working as one would expect.
It must be a timing issue. This is rather different, its more like a data cleanup.

 

[lameid]

Timing... Unless you are doing something very specific that turns on some Asynchronous execution, I would expect Access to run Synchronously.

That being said, I have seen evil things happen based on OS write cache issues / client side file cahcing (Novel Netware).

In any case, good luck getting it to pause... I think they deprecated the sleep function (waits parameter passed in milliseconds)?