Post reply

Access 2002 on XP sp2 Report flashes and then closes

  • April 7, 2005 at 4:56 am

    #68822

    Every time the report is opened it flashes on the screen and then closes, no errors. I am dynamically setting the application printer since these are part tags and not all of my customers have the same label printer. I also dynamically set the RptName for the correct printer. Here is the code:

      Set prt = Application.Printers(PrinterDevice)

      Set rpt = Reports(RptName)

      rpt.Printer = prt

    This issue I suspect is due to XP sp2 changes since customers running on XP sp1 are fine. If I have the customer set the default printer to the label printer they can print the report but get the error: There isn't enough free memory to update the display. Close unneeded programs and try again. The tag prints fine though. I did find that if I change the swap file size to a max of 256Meg which is what the machine has I do not get that error. This is not a large report at all, very tiny.

    If anyone knows a fix or has a troubleshooting tip it would be greatly appreciated!

     

  • April 8, 2005 at 8:33 am

    #551535

    m,

    I had a similar problem with my Access app. I re-wrote a stored procedure without setting NoCount ON at the beginning of the SP. This caused the report to open, but then immediately close.  Access, apparently can't handle the return of the number of records affected appropriately, so I turn NoCount on with every SP.

    I have also found that Access does not always return an error message that SQL Server generates. To fix this, I have to catch the error in VB and return to the user.

    As for memory problems, whenever our users have memory problems with Access (or any program for that matter), it's almost always due to an infestation of spyware, etc. In one case it was corrupted memory stick.

    Don't know if any of these things will help eliminate your problem, but I hope they help in some way.

    Best Regards,

    Kyle

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply