Access 2007 to office 365/Access 2019 VERY SLOW

%3CLINGO-SUB%20id%3D%22lingo-sub-770938%22%20slang%3D%22en-US%22%3EAccess%202007%20to%20office%20365%2FAccess%202019%20VERY%20SLOW%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-770938%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20there%2C%3C%2FP%3E%3CP%3EFirst%20off%20I%20am%20not%20an%20Access%20guy%20at%20all.%20I%20have%20been%20asked%20to%20help%20figure%20out%20why%20an%20MS%20Access%20db%20that%20was%20tolerable%20in%20ms%20access%202007%2C%20speed%20wise%2C%20is%20now%20really%20slow%20in%20Access%202019%20on%20MS%20Server%202016%20Standard.%20We%20have%20upgraded%20to%20office%20365%20office%202019%20and%20since%20doing%20so%20the%20performance%20has%20nosedived.%20There%20are%203%20users%20working%20off%20a%20Windows%202016%20Server%20Standard%20with%20remote%20desktop%2Fterminal%20server.%20Everything%20else%20seems%20good%20to%20go%20but%20this%20database%20is%20driving%20the%20staff%20nuts.%20If%20they%20click%20a%20button%20it%20can%20take%2060%20%2B%20seconds%20to%20open%20the%20field%2Ftable.%20Any%20thought%2C%20suggestions%20or%20help%20is%20greatly%20appreciated%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-770938%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2007%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3E2019%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAccess%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EServer%202016%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-771839%22%20slang%3D%22en-US%22%3ERe%3A%20Access%202007%20to%20office%20365%2FAccess%202019%20VERY%20SLOW%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-771839%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F381207%22%20target%3D%22_blank%22%3E%40RAWFISH66%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWithout%20knowing%20details%20about%20the%20database%20it%20is%20difficult%20to%20advice%20you%20about%20it.%3C%2FP%3E%3CP%3EIn%20general%20I%20can%20sugest%20that%20converting%20the%20database%20to%20version%202019%20would%20be%20something%20worth%20trying.%3C%2FP%3E%3CP%3ECreate%20a%20new%20database%20in%20Access%202019%20and%20import%20everything%20from%20your%20%22old%22%20database%20into%20your%20new%20one.%26nbsp%3B%20If%20there%20are%20compatibility%20problems%20they%20will%20be%20mentioned%20during%20the%20importprocedure.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGreetings%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMarcel%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

Hi there,

First off I am not an Access guy at all. I have been asked to help figure out why an MS Access db that was tolerable in ms access 2007, speed wise, is now really slow in Access 2019 on MS Server 2016 Standard. We have upgraded to office 365 office 2019 and since doing so the performance has nosedived. There are 3 users working off a Windows 2016 Server Standard with remote desktop/terminal server. Everything else seems good to go but this database is driving the staff nuts. If they click a button it can take 60 + seconds to open the field/table. Any thought, suggestions or help is greatly appreciated :)

1 Reply
Highlighted

@RAWFISH66 

 

Without knowing details about the database it is difficult to advice you about it.

In general I can sugest that converting the database to version 2019 would be something worth trying.

Create a new database in Access 2019 and import everything from your "old" database into your new one.  If there are compatibility problems they will be mentioned during the importprocedure.

 

Greetings,

 

Marcel