I have an issue that I am hoping has a solution that does not [nobr]require[/nobr] a code change. I have a crystal report that uses a custom paper size. The custom paper size needs to be created in server properties and in the [nobr]development[/nobr] environment when this is set up everything [nobr]works[/nobr] fine. When I go to the [nobr]test[/nobr] environment (different server)...it does not [nobr]work[/nobr]... it defaults to a paper size that is not compatiable and the one page report [nobr]prints[/nobr] on many pages. When I open the report in crystal on the test machine and save the rpt with the proper paper size it works fine in the test environment. When I go to the next environment the same thing happens. I found the following site that suggests that Crystal stores the id of the paper size rather than the name, which makes sense based on what I am saying because the paper size names all match. (http://social.msdn.microsoft.com/Forums/en/vscrystalreports/thread/e16a1630-ad0c-4fda-8351-16e0807072eb). The code here would [nobr]work[/nobr] but I do not have access to change the code where this would need to go. Since there are a few terminal servers involved in the transaction...I cant just open the report in Crystal on the machine and save. If someone has a system way of getting around this or has another idea, please let me know. Thanks
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!