Error message when OLE operation takes too long

[SBendBuckeye]

I am running an Access query from an Excel macro. The Access app imports 3 tables, combines them with a query and then exports them back out to Excel as 1 file.

Due to the size of the files, I get the following message periodically on the Excel side:

Microsoft Excel is waiting for another application to complete an OLE action

It does not stop the Access code but I would like to prevent it if I can.

Any ideas or suggestions out there?

Thank you!

 

[BrainB]

Aplication.DisplayAlerts = False

Don't forget to reset it to True afterwards.

Regards
BrianB
** Let us know if you get something that works !
================================

 

[mavest]

Hi All!!

I'm having a similar problem, but a little deeper. I have been using the

Application.DisplayAlerts = False

and toggling it back to true right after the OLE action. However, the other software is hanging up. Also Excel is hanging.

This of course does not happen on my computer (fairly fast running Windows NT, Excel 97), but does on my customer's running Windows 2000 and Excel 2000.

Any ideas??

-Mike

 

[SBendBuckeye]

I helped the situation above a little bit making multiple calls to Access. So instead of importing all 3 files and then running a query to combine them and export them to a different file, I broke it up into separate components.

Having the Access application object created, closed and recreated more frequently seemed to help. I hate solutions like that but it seems to work.

FYI, in Office97 it runs in 35 minutes, in Office2000 it runs in 2 minutes so maybe you should encourage your clients to upgrade at least one machine.

Good Luck!