Access 2013 is working extremely well at runtime, however development is substantially more time consuming due to a prolonged delay (up to several minutes) when moving a query from design view to datasheet view, or a form from design view to form view. I have experienced this delay with standalone databases as well as databases with linked tables to other Access database tables and with SQL server database tables.  I have never experienced this type of delay with prior versions of Access.  I most recently migrated from Access 2010 to Access 2013. 

MY OS is Windows 7  64 bit.  Microsoft Office 2013 is the fully installed 32 bit version.  I have 16 gigs of RAM on my desktop with a NVIDIA Quadro 2000 display card, all my applications are designed to run locally.

Hi,

I would like to know the details:

• Did this issue occur with a new/blank database?
• Did these database include some macros?

If this issue not occur with a new database, I recommend you try to "Compact and repair" Access database.

Then, based on your description, the issue also may be caused by the Linked table. Please check the "Always prompt for new location" option.

Next, is the printer a network printer or a network printer that is off line? Access during design mode for the forms will attempt to ask for information about the printer. If that printer is not attached, or on the network, then often a large delay will occur. Please try to set the default printer to a local PDF printer driver.

Hope it's helpful.

Regards,

George Zhao
Forum Support
________________________________________
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click "tnfsl@microsoft.com"

This issue is happening with both existing databases and new blank databases, both with and without linked tables.  No macros are in use.  I tried compact and repair, insured printers are on line, and changed to local PDF print driver as my default printer.   Issue still persists. 

Hello ,

Thank you for your post.

This is a quick note to let you know that we are performing research on this issue.

Regards,

George Zhao
Forum Support
________________________________________
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click "tnfsl@microsoft.com"

I have the same issue, and resolved it until reinstall.

I have had the same issue with Access for months, both before and after upgrading from Office 2010 to Office 2013 to Office 365.  I have tried reinstalling, but the end results have been the same.  I have tried all the fixes suggested above with no improvement.  The only workaround I have found is to open objects (queries, tables and forms) in design view, make any needed changes, and then save and close.  Then I can open the same object (query, table or form) in normal view with no trouble.  If I try to go directly from design view to normal view, it may take as long as 10 minutes.  Needless to say, having to constantly close and reopen objects that currently under development is extremely time consuming and annoying.  Fortunately, my customers do not use design view.  Please advise.

V/r, Bob Park

I am using the same work around, design, save, close and open.  I am opening a Microsoft Support Case to try and resolve.  I do not have this issue on my home computer, so my intuition leads me to believe its a network security issue.

I also am having the same problem under identical installation and use patterns as the previous posters.  One additional bit of info - I have noticed that the long delay only occurs when MORE THAN 1 object is open IN DESIGN view.  Even simply switching between the 2 design-view windows will cause the 2-3 minute delay.

With that being said - one simple workaround is just to make sure you close any objects that are in design view before opening another.  Not an acceptable solution, but better than the delay when there is no other choice.

• Edited by Unowho247 14 hours 29 minutes ago
• Proposed as answer by George.Zhao CHNMicrosoft contingent staff, Moderator 6 hours 30 minutes ago

I also am having the same problem under identical installation and use patterns as the previous posters.  One additional bit of info - I have noticed that the long delay only occurs when MORE THAN 1 object is open IN DESIGN view.  Even simply switching between the 2 design-view windows will cause the 2-3 minute delay.

With that being said - one simple workaround is just to make sure you close any objects that are in design view before opening another.  Not an acceptable solution, but better than the delay when there is no other choice.

• Edited by Unowho247 Thursday, April 09, 2015 4:59 PM
• Proposed as answer by George.Zhao CHNMicrosoft contingent staff, Moderator Friday, April 10, 2015 12:58 AM

I also am having the same problem under identical installation and use patterns as the previous posters.  One additional bit of info - I have noticed that the long delay only occurs when MORE THAN 1 object is open IN DESIGN view.  Even simply switching between the 2 design-view windows will cause the 2-3 minute delay.

With that being said - one simple workaround is just to make sure you close any objects that are in design view before opening another.  Not an acceptable solution, but better than the delay when there is no other choice.

• Edited by Unowho247 Thursday, April 09, 2015 4:59 PM
• Proposed as answer by George.Zhao CHNMicrosoft contingent staff, Moderator Friday, April 10, 2015 12:58 AM

I also am having the same problem under identical installation and use patterns as the previous posters.  One additional bit of info - I have noticed that the long delay only occurs when MORE THAN 1 object is open IN DESIGN view.  Even simply switching between the 2 design-view windows will cause the 2-3 minute delay.

With that being said - one simple workaround is just to make sure you close any objects that are in design view before opening another.  Not an acceptable solution, but better than the delay when there is no other choice.

• Edited by Unowho247 Thursday, April 09, 2015 4:59 PM
• Proposed as answer by George.Zhao CHNMicrosoft contingent staff, Moderator Friday, April 10, 2015 12:58 AM

This is a temporary workaround at best, but it's better than nothing.  This will not work when you are working on a form in design mode, and then want to edit a query on a subform contained on the form.  I have been opening up the source object in design mode, making my changes, saving and closing the object and then opening up the form to avoid the lengthy delay.

Me too I have exactly the same problem and I adopted the same solutions (that are not solutions but temporary tricks) than Harold.

I made new db and used db coming from access 2003, 2007, etc. but I have the same issues: wasting time waiting for a restart of the application (because during the time access say to be not working).

Did you find a fix ?

I installed the exact same MSOP Plus media on a non-networked computer, and none of the delay issues are occurring.  The problem seems to be in our company's network group policy, and our virus protection software.  Microsoft's development team is treating the issue as a bug and will hopefully create a fix.

Update on the resolution of this problem.  We have determined that our company's network group policy is not creating this delay issue.  The issue is with Symantec Endpoint Protection interacting with Access.  The issue only happens when the "Property Box" is open in Access.

Would you pleases elaborate more. Which Property Box?

AKA Property Sheet, - the box that allows the user to control the property settings on any object.

Thank you.  This solves many latency issue I have been having.  Closing the Property Sheet, removes any lag when switching "tabs" and my queries which were slow are now fast.

This explains why since transitioning to 2013 I faced a major slow down.  In 2010 the property sheet is default to closed.

We are opening a support case with Symantec to try to get issue resolved.

The issue has been traced to the Application and Device Control feature set within Symantec EndPoint Protection.  We had to build a custom install package without that features set to resolve the issue.  Symantec is revewing debug log data to try and determine what is causing the delay within that module. 

Sorry it is not restricted to Symantec. I have the same issue and no symantec installed. I am going through all of my services and installed programs to see if I can get this corrected. ? vpns? Printers? I will update you. Please keep this issue going.

Deleted all vpns, rebooted froze the computer, reinstalled them and rebooted. Windows update, restarted took 30 mins to update on reboot. Appears to fix it.