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
B

BradBloom

@BradBloom
About
Posts
1
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Blaming Crystal Reports
    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

    Clever Code csharp visual-studio help announcement
  • Login

  • Don't have an account? Register

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