Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Other Discussions
  3. Clever Code
  4. Blaming Crystal Reports

Blaming Crystal Reports

Scheduled Pinned Locked Moved Clever Code
csharpvisual-studiohelpannouncement
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    B Offline
    BradBloom
    wrote on last edited by
    #1

    We recently upgraded a working project to .NET 2 Framework/Visual Studio 2005. We have a Crystal Report that prints to a custom size paper (or several) and it would never line the next page properly or eject the page to far (on a dot matrix printer). It would often reset the selected printer's paper size back to 8x11. The report would print properly on the development machine but not on the compiled client version. We immediately pointed our fingers at Crystal Decisions and all the versions, patches, hot fixes, msi files, etc:^). Tech support calls, emails, sending code to them, them sending code to us. Two weeks went by and nothing worked. I finally did a Google search on 'Custom printing problems' (which I should have done in the first place). I found articals that pointed to a known problem with the .NET 2 Framework and had several different ways or examples to get around it. :doh: bbloom

    P 1 Reply Last reply
    0
    • B BradBloom

      We recently upgraded a working project to .NET 2 Framework/Visual Studio 2005. We have a Crystal Report that prints to a custom size paper (or several) and it would never line the next page properly or eject the page to far (on a dot matrix printer). It would often reset the selected printer's paper size back to 8x11. The report would print properly on the development machine but not on the compiled client version. We immediately pointed our fingers at Crystal Decisions and all the versions, patches, hot fixes, msi files, etc:^). Tech support calls, emails, sending code to them, them sending code to us. Two weeks went by and nothing worked. I finally did a Google search on 'Custom printing problems' (which I should have done in the first place). I found articals that pointed to a known problem with the .NET 2 Framework and had several different ways or examples to get around it. :doh: bbloom

      P Offline
      P Offline
      Peter Wone
      wrote on last edited by
      #2

      Crystal Reports is extremely well named - it's fragile and expensive, no sensible person would use it for anything but a very special occasion and it is typically bought by other people who don't have to look after it.

      PeterW -------------------- If you can spell and use correct grammar for your compiler, what makes you think I will tolerate less?

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups