AAI

Am customising the Avery 5263 walk through labels to print on Avery 7165 as the 5263 cannot be purchased in the UK.
I Have been successful apart from one problem.......I can only print 3 rows, I need 4 rows I have the option to change the columns but not rows.

Can anyone help?

RickC

Originally Posted by AAI

Am customising the Avery 5263 walk through labels to print on Avery 7165 as the 5263 cannot be purchased in the UK. I Have been successful apart from one problem.......I can only print 3 rows, I need 4 rows I have the option to change the columns but not rows. Can anyone help?

This has to do with the fact that all reports are currently set to US Letter paper size. We will be exposing property in an upcoming SP for users to change on custom reports (New Report Wizard in the designer).

Until then, here's a VERY unsupported "As Is" workaround (custom reports/ latest patch only):

It only works for SI5 installations of the latest patch.

1. Create and publish your custom report.
2. Close the reporting center.
3. Broswe to the following location:
   XP: C:\Documents and Settings\{current user name}\Application Data\D-Tools\SI5\Reports
   Vista: C :/Users/{current user name}/AppData/Roaming/D-Tools/SI5/Reports/
   NOTE: {current user name} is your account on the PC.
   
4. Locate the file "ReportData.XML"
5. Make a copy of this file *DO NOT simply rename this file*. Name the backup copy anything EXCEPT reportdata.bak, chances are, there's one there already anyway. This is your backup in case the following steps leave you out in the cold.
6. Open the reporting center.
7. Export all of you custom reports. You can do this in a single export. This should be stored safely in case things go awry.
8. Export the report you want to modify (note the name of the zip file and location where it is saved).
9. Use Windows Explorer to browse to the newly created export file.
10. Make a backup copy of this file. I can't stress this enough!!!
11. Right Click on the original Zip file and select "Extract All".
12. In the folder where the zip was extracted (most likely a sub folder where the zip was saved, you will see 2 or more files
13. Open the file called ReportData.XML in notepad or some other text/xml editting tool.
14. Replace all instances of the string "<dtrd:PaperSize>Letter</dtrd:PaperSize>" with "<dtrd:PaperSize>A4</dtrd:PaperSize>" (quotes not part of the find/replace)
    
    For all papersizes see: http://msdn2.microsoft.com/en-us/lib...paperkind.aspx
    
15. Save the ReportData.XML file
16. Rezip up all files (the reportdata.xml and all RPX files) that were extracted.
17. Click the "Import Reports" toolbar
18. Browse to the new zip file (the one with the modified ReportData.xml file).
19. Click open and run the report.

Now...in case of emergency, DO NOT panic!!!!

If for some reason things just don't seem right, follow these steps very carefully.

1. Close the reporting center AND Navigator (if open)
2. Browse to the following location:
   XP: C:\Documents and Settings\{current user name}\Application Data\D-Tools\SI5\Reports
   Vista: C :/Users/{current user name}/AppData/Roaming/D-Tools/SI5/Reports/
   {current user name} is your account on the PC.
   
3. Locate the file "ReportData.XML"
4. Delete it.
5. Locate the copy you made in step 5 above and rename it to reportdata.xml.
6. Restart the reporting center. You should be back to step zero.
7. If you don't seem to see your custom reports, you should be able to export them all back in if you followed step 7 above

A couple of things...

• If you have a bunch of custom reports, you can export them all and do this in one step. Test it on one first though)
• This is NOT for the faint of heart, but it's not that hard either, just be careful.
• Lastly, this is "As Is" and unsupported. The worst case scenario is that the core ReportData.xml file gets totally hosed up (the one in your app data folder). If so, delete it completely and restart the reporting center, you'll be back at square one like a brand new install.

Give it a try, be careful....

Again, we are going to expose a UI setting in an upcoming patch (not sure which yet) so users don't have to go through this (admittedly) painful process.

-R