Skip to main content

Using Half Size Form in Crystal Reports

i have a hard time trying to solve this one

scenario: at first, we using Letter format to print Delivery Order and Invoice..it run smoothly and in CR we just using Letter as the Page Setup..

now new paper format is coming which is half of the Letter size
at first i thougt it is easy because we only need to create new paper size on Server Properties under Printer and Faxes then use the new size at Paper Size in CR then redesign it to fit but it all when wrong, eventhough it display correctly but when i want to print it, it turn up everything that vertical become horizontal..very2 strange behaviour

so i give using CR.PrintReport method..i ended up format it to .rtf then print it using this code
Dim oDoc As New ReportDocument
Dim sFileName As String = String.Empty

oDoc.Load(_ReportPath)

'must use this line to make sure it print using the new size
'credit goes to Ali from dotnet.netindonesia.net
Dim printDoc As System.Drawing.Printing.PrintDocument = New System.Drawing.Printing.PrintDocument

Dim i As Integer

Dim rawKind As Integer = 0

For i = 0 To printDoc.PrinterSettings.PaperSizes.Count
If printDoc.PrinterSettings.PaperSizes(i).PaperName = "NEW_SIZE_PAPER" Then

rawKind = CInt(GetField(printDoc.PrinterSettings.PaperSizes(i), "kind"))

Exit For
End If

Next i

oDoc.PrintOptions.PaperSize = CType(rawKind, CrystalDecisions.Shared.PaperSize)
'oDoc.PrintToPrinter(1, False, 0, 0)

Dim CrExportOptions As ExportOptions = New ExportOptions()
Dim CrDiskFileDestinationOptions As DiskFileDestinationOptions = New DiskFileDestinationOptions

Dim CrFormatTypeOptions As PdfRtfWordFormatOptions = New PdfRtfWordFormatOptions
CrDiskFileDestinationOptions.DiskFileName = sFileName

CrExportOptions.ExportDestinationType = ExportDestinationType.DiskFile
CrExportOptions.ExportFormatType = ExportFormatType.RichText
CrExportOptions.DestinationOptions = CrDiskFileDestinationOptions
CrExportOptions.FormatOptions = CrFormatTypeOptions

oDoc.Export(CrExportOptions)

Dim myProcess As New Process()

myProcess.StartInfo.FileName = sFileName
myProcess.StartInfo.Verb = "Print"
myProcess.StartInfo.CreateNoWindow = True
myProcess.StartInfo.ErrorDialog = False
myProcess.StartInfo.WindowStyle = ProcessWindowStyle.Hidden
myProcess.Start()

it print correctly now, hope it turn up well in Live

see u
Labels:

Comments

Post a Comment

Popular posts from this blog

SBO - Internal Error (-5002) Occured in Inventory Transfer

this is something that not well documented in SBO, it took me several hours to look at Google and can't find anything about it. Thank God friend of mine got answer for this one.So the Sympton is something like this, u need to make Inventory Transfer for Batch Item and Serial Item in one single Transaction so the Transaction is the combination of it. ex in detail lines: 1. Serial Item 2. Batch Item 3. Batch Item 4. Batch Item 5. Serial Item 6. Serial Item . When u reach this code oStockTransfer.Add it will return an error "Internal Error (-5002) Occured". This is because ur details is not in order, meaning u need to order the line with combination of Batch first then Serial or Serial first then Batch so be careful with this thing :D see u
Post a Comment
Read more

Crystal Report 2010 - Failed to load database information

"Failed to load database information" error when i try deploy my program with CR 2010 using TTX file as report definition this is because there is missing .dll, call "CRDB_FIELDDEF.DLL"..u need to manually copy the file to "C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86" folder then the report is loading again it said that TTX is old tech but i'm still using it because i don't need to connect the report to any DB, but until i found new one to replace :D check this link to read it [EDIT 25 Jan 2011] i think i'll using ADO.NET Dataset next time :D until then
2 comments
Read more

Resolve Collation error in SQL Server

i often get this error when trying to JOIN some table Cannot resolve the collation conflict between "SQL_Latin1_General_CP850_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation. u need to use COLLATION when performing the JOIN, something like this SELECT field1 FROM table1 INNER JOIN table2 ON table1.field3 COLLATE DATABASE_DEFAULT = table2.field4 COLLATE DATABASE_DEFAULT i found this when trying to JOIN, maybe it affect other areas..until i found one see u
Post a Comment
Read more