I split my database into a front and back end. The split went okay, no issues. After the split, the program still runs well, however, if I need to make changes to a form in form view, it suddenly starts to go very slow. 30 - 40 seconds go by after you click an item until it lets you edit it or change it. This was not the case before the split. Any ideas as to what might be causing it?
-
-
There are many reasons why this could be happening.
Where are the front end and back end of your database located? Are they both on a network drive?
Have you checked that your vba code is all compiled? It may also be worth checking the file size of your front end it might give us some clues.
Overall though it could simply be down to poor design of the database, which may help if you could post an example of the database here. -
The back end will be on a network drive, the front end on the users private drive.
All the VBA code, which isnt really much, is compiled.
The accde file is a 4mb file.
I wish I could post a copy of the database, but due to security where I work, i am unable to.
If there are general areas that would make it slow, other than the ones you have already suggested, it could lead me doqwn the right path.
ThanksComment
-
Solution/
I strongly believe that this due to using tables as forms/reports recordset or recordsource. Just create queries based on the same tables (mirrors) and change the recordset of forms and reports accordingly and you are done.
The reason is that queries stay in the FrontEnd after split --> direct connection; where tables reside on the other end.
Regards,
AliComment
-
To be honest I wouldnt say so. I use tables as the record source on some of my forms, not all but most and I havent noticed any detriment at this point. Granted queries should run quicker but that is only if they have been compiled with the latest indexes otherwise they would probably run slower if they are very outdated.
Here is a good list of things to check for to improve speed:
Comment
Comment