Search results

The reason is because the loop is based upon an ever changing query. More important is the fact that this blazes right along on a stand-alone machine with quite acceptable times. The need in my opinion is to search out what Access may be interacting with on Windows Server which may be...

The loop: 1) executes an ADODB open 2) executes an ADODB edit 3) executes an ADODB update 4) executes an ADODB close ... 5,000 times?

A puzzling situation. We have an Access program that contains a simple loop that does an ADODB open, edit, update then close. This program runs successfully and with reasonable speeds (about 8 minutes for 5000 trips through the loop) on all versions of MS Access 2000 and 2003 (regardless of...