boblarson
Smeghead
- Local time
- Today, 02:59
- Joined
- Jan 12, 2001
- Messages
- 32,059
Welcome to Access World Forums. Glad you were able to get something out of here that would help you.
Slow performance (REALLY slow!)
- Thread starter shacket
- Start date
Man! You guys saved me tons of time. I had the same problem. I was working on a db and reports were fine. I had to turn off my wifes computer for some maintenance, which has our shared printer on it. Needless to say, when i went back to working on my db, my reports were rediculously slow. I tried new blank db's, etc., etc., to no avail. After reading the post, I just temporarily removed the printer on my pc and voila. Thanks so much for the tip. It was driving me crazy.
boblarson
Smeghead
- Local time
- Today, 02:59
- Joined
- Jan 12, 2001
- Messages
- 32,059
Welcome to Access World Forums and thank you for actually SEARCHING for an answer instead of just posting immediately. That is incredibly rare, yet highly appreciated. Glad you were able to sort the problem.
Quick Workaround
Believe it or not, a quick workaround to this problem is simply to open a table and leave it open while you're working on some other form.
In a nutshell, the reason this works is that when you work on a form or report that's accessing a data repository somewhere else on the server, that server winds up doing a ton of checks to figure out whether you've got permission to do what you're doing. If you simply open up a table, that establishes your permissions, and the server won't feel the need to check again until you close it. Yeah, it's kind of a voodoo trick, but it works. Just open up some other table while you're working, and leave it in the background somewhere.
Hope this helps keep someone from pulling their hair out
Believe it or not, a quick workaround to this problem is simply to open a table and leave it open while you're working on some other form.
In a nutshell, the reason this works is that when you work on a form or report that's accessing a data repository somewhere else on the server, that server winds up doing a ton of checks to figure out whether you've got permission to do what you're doing. If you simply open up a table, that establishes your permissions, and the server won't feel the need to check again until you close it. Yeah, it's kind of a voodoo trick, but it works. Just open up some other table while you're working, and leave it in the background somewhere.
Hope this helps keep someone from pulling their hair out
DCrake
Remembered
- Local time
- Today, 10:59
- Joined
- Jun 8, 2005
- Messages
- 8,626
Simple Software Solutions
Can I just add a littel bit of input to this thread... When I encountered this problem I found that if the form or report was a bound form or report then it became sluggish. This is one of the reasons I aviod them.
CodeMaster:
Can I just add a littel bit of input to this thread... When I encountered this problem I found that if the form or report was a bound form or report then it became sluggish. This is one of the reasons I aviod them.
CodeMaster:
- Local time
- Today, 05:59
- Joined
- Feb 19, 2002
- Messages
- 47,225
You may as well be working in Winforms if you are not taking advantage of the RAD features of Access. The biggest benefit of using Access is bound forms and reports.
Your slowness was likely caused by not limiting the data that the form was displaying. Just opening a form bound to a table or a query with no selection criteria just opens a pipeline to the server and data is dragged over the network until Access has sucked over the entire recordsource.
Your slowness was likely caused by not limiting the data that the form was displaying. Just opening a form bound to a table or a query with no selection criteria just opens a pipeline to the server and data is dragged over the network until Access has sucked over the entire recordsource.
marceloaragao
New member
- Local time
- Today, 04:59
- Joined
- Jan 16, 2010
- Messages
- 1
I believe that the printer that is set as 'default printer' on Windows must be accessible.
The way that I solved that was setting my 'PDC Creator Printer' as default printer because my a network printer was not accessible.
In case you do not have one you can use this one http://sourceforge.net/projects/pdfcreator/ or make sure that your 'default printer is accessible'
Now...ms access is again fast !
Regards,
Marcelo
The way that I solved that was setting my 'PDC Creator Printer' as default printer because my a network printer was not accessible.
In case you do not have one you can use this one http://sourceforge.net/projects/pdfcreator/ or make sure that your 'default printer is accessible'
Now...ms access is again fast !
Regards,
Marcelo
Another satisfied developer
I just want to echo the sentiments of the others here. I changed my default printer and all is well now.
It's funny how a post from years ago still is paying dividends. Thanks so much for saving me time!
I just want to echo the sentiments of the others here. I changed my default printer and all is well now.
It's funny how a post from years ago still is paying dividends. Thanks so much for saving me time!
Hi,
I felt that I had to contribute. This had me so frustrated I could not do any design work at all. The default printer change did not do it for me. Opening a small random (linked BE) table and minimizing did the trick! Whew!
Such a simple solution once you know.
Thanks!
Ryan
I felt that I had to contribute. This had me so frustrated I could not do any design work at all. The default printer change did not do it for me. Opening a small random (linked BE) table and minimizing did the trick! Whew!
Such a simple solution once you know.
Thanks!
Ryan
Similar threads
