![]() |
|
|
|||||||
|
|
|
LinkBack | Thread Tools | Display Modes |
|
#1
|
|||
|
|||
|
Hi everyone!
My problem: There isn't enough free memory to update the display. I looked all over the internet about this error but without any success. Facts are: 1. I keep getting this error anytime I try to Print or Print Preview or export to PDF an Access Report (same error for printing Forms and maybe other objects). 2. I received this error when using Office 2007 with the same mdb and also after upgrading to Office 2010. 3. The same mdb on any other computer works perfectly. I can do Print, Print Preview or whatever I want. This seems to be related to this laptop I am using. 4. Resources are not a problem on this laptop: 3Gb RAM, Paging: 1Gb on sys drive C and 2Gb on D. The other machines have less. I could really use some help because it is annoying to work on this machine, email the mdb on another machine (or to a friend) then export to PDF and then send me back the PDF in order to print it. Any suggestions are welcome. Thanks a lot, Bosch Last edited by bosch; 03-13-2010 at 06:57 AM. Reason: updated thread title |
|
#2
|
|||
|
|||
|
I've had this too - and it is a pain. Unique to 1 PC only - - - and in my case - reboot would usually clear. ...but not always....
anytime a Report won't work one has to be suspect of the print driver; as the print driver interacts with Access even when opening in Preview mode; plug a printer to your laptop - make sure it is your default printer and working ok....and then try and see if the problem still occurs... another idea; while you have loads of capacity - it is always possible you have something running that is causing the conflict; perhaps a CRM application has embedded sqlserver or something....so be sure to review all that stuff - even potentially turning off your antivirus stuff - - for testing purposes... please post what you find..... |
|
#3
|
|||
|
|||
|
Quote:
Quote:
I have also installed BullZip PDF Printer and set it to default and still nothing. Those 2 printer drivers above are on the other laptop where the reports open fine. I once had an IBM network printer and I only used it a few times, at the office and i remember i had some issues with it but i cannot correlate the time when i installed the printer with the date when the reports stopped working. Maybe it would be an idea to clear all the printer drivers that were ever installed, or whatever resides in Sys32/spool ? There are a few folder there that do not seem quite right. I don't know, though, what can be deleted and what cannot... Quote:
Anyway, I have tested it also right after logging in, with all unnecessary processes killed (procexp is my friend) and still got the same result. I tried with or withour antivirus, firewall, antispyware, etc. I have even updated the display drivers (I was sure that would solve it but i was wrong). I am positive that it has nothing to do with the RAM or with the message itself. I think you are right with the printer driver idea but I don't know what to do next: like I said, i have the same printers on the other computer and they are set up exactly the same way. Very strange.... |
|
#4
|
|||
|
|||
|
well you've jumped into alot of peripheral things pretty fast;
have you deleted that FE and installed a new FE? that's a basic thing. assuming that the report has a record source that is a query; are you able to open that query yourself manually by itself ok? if so - I would then make a totally new basic report and see how that goes. if some reports work fine - but just one is bombing - then I would focus on that single report object; if all reports are bombing I would focus on deleting all print drivers - and then set up one single printer with it attached..and see then if reports will run..... |
|
#5
|
|||
|
|||
|
sorry
![]() Quote:
Quote:
Creating a blank MDB with a blank report raises the same error... Quote:
Thanks for taking the time to read.... ![]() Bosch |
|
#6
|
|||
|
|||
|
FE is front end. multiuser dbs are split between an FE that resides on each user's pc and the BE which contains the tables and are linked/shared by all users.
if your FE is corrupt - deleting it and replacing it with a copy of another FE might fix your problem... |
|
#7
|
|||
|
|||
|
Quote:
Well, in my case the db is not multiuser, everything resides in one mdb... I will try playing with the registry until I remove the print drivers. Maybe Access has a region of its own where it keeps printer settings, no matter which is the default printer... |
|
| Bookmarks |
| Tags |
| error, print, reports |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
Where to find free Beginner Access Tutorials
|
newtoAccess | Access | 4 | 11-23-2009 10:13 AM |
| access 2003 on vista Out of Memory Problem | skbrede | Access | 0 | 07-25-2009 06:28 AM |
| I am using Access. How can I clear cache memory? | komralph | Access | 0 | 01-09-2009 12:10 PM |
| Out of Memory | Norman Masson | Access | 0 | 12-29-2008 08:09 PM |
| Free Billing Application | khalodaaa | Access | 1 | 06-23-2007 03:43 AM |