Mouse pointer/cursor flickering when running vba code in the background

[merebag]

I have an annoyance when running my vba code (which was converted from an Access Data Project in Access 2010) on my Access 2013. The problem is, when I run routines that do a lot of SQL selects and updates when launched, the mouse pointer just toggles quickly showing busy (with the circle around it). I have used DoEvents on my 2010 Access data project and it works flawlessly. However, in 2013, I can't seem to get away from this annoyance.

Has anyone come up with a sure-fire way of eliminating this? I want the end user to still be able to do other things while this process (which may take a few minutes) runs. However, when they have the mouse pointer flashing and acting busy, its a problem.

Jeff

[RuralGuy]

You do know that MS Access is still Single Threaded, right?

[merebag]

Yes... I am aware that it is single threaded, which is a pain, but with the doevents, it seemed to run in the background fairly well (with Access 2010 ADP that is)... Now that I am using ODBC DAO style connectivity, the doevents, while it does work, has the flickering.

[RuralGuy]

I want the end user to still be able to do other things while this process (which may take a few minutes) runs.

What else did you want the user to do? Nothing in access will work until that single thread is complete.

[RuralGuy]

Ahh...you were using Stored Procedures in the SQL backend right? The work was accomplished in SQL Server rather than with the MS Access Front End. Are you still using SQL Server as your Back End?

[merebag]

Yes, I am still solely on a MS SQL server backend with ODBC connectivity. However, I don't use many stored procedures. The issue I am referring to is using DAO recordsets along with .runsql commands.

[aytee111]

What exactly do you mean by

I want the end user to still be able to do other things

? Can you give an example?

[RuralGuy]

I'm no expert on the ADP but I'll bet it was tightly integrated with SQL Server and used Stored Procedures whenever possible which took the load off of the FE. As I asked a bit ago, what else did you want the user to be able to do while this is executing?

[merebag]

This routine that I want to run in the background, (well, even though its single threaded it can somewhat simulate being ran in the background), does a lot of of table searches and updates. Its an end of month report to produce bills and such. This process takes about 2 to 3 minutes to run. That is not the problem. The problem comes when the process is launched and the end user wishes to do something else in the application while it runs. In ADP, using the doEvents, it released the process so the end user can do other things in the app while it ran. It STILL does that in my new app with Access 2013. The problem is, the cursor/mouse arrow is flickering like its busy, even though the end user can still click on other things to run. The flickering stops as soon as the original process is done.

[RuralGuy]

I'm afraid I'm out of ideas here. Good luck with this project.

[merebag]

Ya... it's a strange one....... an annoyance.. At least it still works..... thanks anyways