[AccessD] Printing in Access 2002

...having just gone through a week long exercise with a brand new $18K Minolta Printer/Copier at a client, I can vouchsafe that lots of XP drivers are buggy ... had to actually install a W2K laptop and print from it to get critical work out the door ...the only thing that I can tell you is that if the printer driver is missing the MS Certified for Windows XP logo there is probably a reason for it besides the cost :(((((((
 
William Hindman
"War is an ugly thing but not the ugliest of things; the decayed and degraded state of moral and patriotic feelings which thinks that nothing is worth war is much worse. A man who has nothing for which he is willing to fight, nothing which is more important than his own personal safety, is a miserable creature and has no chance of being free unless made and kept so by the exertions of better men than himself."  John Stuart Mill 

  ----- Original Message ----- 
  From: Jim Dettman 
  To: accessd at databaseadvisors.com 
  Sent: Wednesday, April 09, 2003 3:16 PM
  Subject: RE: [AccessD] Printing in Access 2002


  Try installing a very generic driver, such as a HP Laser JET III (assuming this is a Laser) and printing the report against that.  Buggy print drivers seem to be becoming an issue again.

  If that fixes it, then you might want to try altering some of the original driver settings (such as spool format), or report properties (such as Layout For Print and Fast Laser Printing).

  Jim Dettman
  President,
  Online Computer Services of WNY, Inc.
  (315) 699-3443
  jimdettman at earthlink.net 

    -----Original Message-----
    From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Liz Doering
    Sent: Wednesday, April 09, 2003 2:42 PM
    To: accessd at databaseadvisors.com
    Subject: [AccessD] Printing in Access 2002


    Dear List,

    We have a client (Bill) who sells a little application to local city governments and comes to us about once a year for tweaks and upgrades.  Today he has spent the whole day at one of his cities, trying to get his app to run on their WinXP/Office XP machines.  (This app was originally developed in 97 and converted to 2000).  Everything is fine except that reports do not run.  Hitting the Preview button causes absolutely nothing to happen.  

    I was thinking that this was a problem with the app, or the conversion to Access 2002, but I don't think so now.  I had Bill create a completely new .mdb, create one table with four fields:  ID, Name, Address, City.  The ID field is an autonumber PK, the rest are text.  Bill used the report wizard to create one simple report from this table, and received the message that "The wizard is unable to create your report".  Creating a report without the wizard produced a little more information, a complaint about a lack of default printer.  (I don't have the exact text of the error message, and I can't get it, because Bill has given up for the day and gone home.)

    We double-checked for a default printer, which there was, but in the hopes of changing something, we deleted all printers and re-installed one, setting that to the default.  The printer will act correctly as the default printer for Word, Excel, etc.  

    Rebooting hasn't helped.  Nor has a re-install of Access.  

    Does anybody know what is going on here?

    Thanks so much,

    Liz Doering 
    Symphony Information Services 
    liz at symphonyinfo.com 
    www.symphonyinfo.com 



------------------------------------------------------------------------------


  _______________________________________________
  AccessD mailing list
  AccessD at databaseadvisors.com
  http://databaseadvisors.com/mailman/listinfo/accessd
  Website: http://www.databaseadvisors.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030409/a9c83542/attachment-0001.html>