Results 1 to 9 of 9
  1. #1
    Star Lounger
    Join Date
    Apr 2002
    Posts
    84
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Error viewing Report (Ac2002)

    Have sent an Ac2000 db to a customer, and he's using it in Ac2002. When he tries to open any of the reports I designed for him, he gets this error:

    Runtime Error 2213: Problem retrieving print information for this object. This object may have already been printed on another printer which is not available. (Or similar wording)

    This is bewildering, and the MS KB is no help. Ideas?

    TIA

    James

  2. #2
    5 Star Lounger
    Join Date
    Jan 2001
    Location
    Newbury, Berkshire, England
    Posts
    712
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Error viewing Report (Ac2002)

    I'm guessing here, but three things spring to mind.

    1) A friend of mine sends me a publisher document periodically and when I load it up publisher tells me that the document is set up with a printer driver that I don't have, would it like me to set it up with the default printer. I think that's right but the terminology might be slightly different. Could be your customer has a different printer set-up, ask your customer what printer driver they are using and set your machine up with the same driver.

    2) I understand that access 2002 has some new features for handling printing this could be the root of your problem. I have no experience with this.

    3) I recall in the past when I have loaded Access on to a new computer, if you try to look at a report in print preview before you have loaded any printer drivers, then Access says you can't view the report because there's no printer set-up. Make sure your customer has at least one printer driver set up on his machine, the same one as yours would be best.

  3. #3
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Error viewing Report (Ac2002)

    Hard to tell without knowing exactly what's going on. A few things to keep in mind are

    1) the printer settings are saved with the report. If the printer is not available on that machine then the other user has to have permissions to modify the design of the report to print it to another printer.

    2) Is your printer on a network drive? Not existent paths like that can create all kinds of upsets on another machine.

    3) How are you distributing the database? If you distribute an MDE front end, then no changes can be made to objects like forms and reports.
    Charlotte

  4. #4
    Star Lounger
    Join Date
    Apr 2002
    Posts
    84
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Error viewing Report (Ac2002)

    Thanks for your comments. I'm sure my customer has a different printer setup to me - but I've been providing Access dbs commercially for several years and never seen this problem before. I've even given Ac2000 dbs to an Ac2002 user (as here), with reports, and had no problems. Perhaps there is a problem with their printer setup, or they have none.

    James

  5. #5
    Star Lounger
    Join Date
    Apr 2002
    Posts
    84
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Error viewing Report (Ac2002)

    Thanks. I intend this db to be a piece of commercial software when I've finished it, distributed as an MDE - so this is something I need to clear up! At the moment it's an MDB, with code passworded and Startup settings to open a form and turn off menus etc (and renamed to .MDE to throw novices off the scent!). My printer, BTW, is a local one. I'm trying to work out what I've done differently here which could have caused a problem, but apart from changing the file extension (!) I can't think of any differences to my usual databases.

    Surely one can distribute MDEs and not fall foul of printer driver problems? I'm sure I have before.

    James

  6. #6
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Error viewing Report (Ac2002)

    All I can suggest is to make sure you set the report up to print to the default printer and provide a toolbar or menubar that pops up the print dialog so he can select a specific printer. Out apps have reports that have to print correctly no matter what the paper size and printer, so we use PrtDevMode extensively and distribute secured mdbs instead of MDE apps. <img src=/S/shrug.gif border=0 alt=shrug width=39 height=15>
    Charlotte

  7. #7
    Star Lounger
    Join Date
    Apr 2002
    Posts
    84
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Error viewing Report (Ac2002)

    > make sure you set the report up to print to the default printer
    That's in Page Setup/Page, right?

    I have an inkling of one possible reason for this problem. I may have created the reports before I set up the default printer on my PC. Aargh. That's the only possible thing I can think of that may be different this time from the dozen+ before.

    > Out apps have reports that have to print correctly no matter what the paper size and printer
    > so we use PrtDevMode extensively and distribute secured mdbs instead of MDE apps
    Sounds like me then. Please excuse the stupid qs, but: "PrtDevMode"? ... and, by 'secured mdbs' do you mean just password-protected code or something more elaborate?

    With much gratitude

    James

  8. #8
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Error viewing Report (Ac2002)

    In AXP, it is possible to create reports without having a printer set up. That wasn't possible in earlier versions.

    Look up PrtDevMode in help. In AXP, there is actually a PrtDevMode and a PrtDevNames property of objects, but I'm not sure it's any easier to use than the API calls to get the information that property represents. As for security, we use Access security. We're still distributing Access 97 apps, so the luxury of password protecting code modules isn't there for us.
    Charlotte

  9. #9
    Star Lounger
    Join Date
    Apr 2002
    Posts
    84
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Error viewing Report (Ac2002)

    Thanks for that. I'm going to make a site visit and recreate reports there I think.

    Cheers
    James

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •