Asynchronous Operations

I

Ivar Svendsen

Hello.

I just discovered why my Access database fails on certain
computers.

I have a continous form used as a data entry page. When
pressing a button on the form header, I run some VBA code
to process the data.

The VBA code reads from a calculated field ( =Sum
(Totals) ) and this is where something starts to really go
wrong.

First thing is that the record is not saved before the
OnClick event handler is called. This is easily fixed by
calling "RunCommand acCmdSaveRecord".

This will (mostly) be enough, but on some computers this
fails too!!! I figured out that Access was doing all the
calculations in the background, and possibly when not
running any code (being idle, that is).

Even calling Form.Recalc produces this behavior. Running
on one certain computer gives a 60% error rate!!!!!!!!!!


Of course --- I have to rewrite my code to use DSum()
reading from the table instead of using the calucated
field. But WHY?? Access XP has just been reduced from a
useful tool to an unreliable pile of crap.




Regards,
Ivar Svendsen
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top