
- #Activereports 7 borderlinestyle code#
- #Activereports 7 borderlinestyle Pc#
- #Activereports 7 borderlinestyle windows#
Again, these issues are not happening for all clients, but enough that it's presenting a problem for them/us. I know I can handle this event and use my own PrintDialog to get around the issue but I'm looking for a more global/less invasive fix. The report displays correctly, but we get the same error "The data is invalid" when printing from the built-in toolbar printer icon. Is there any insight you can give me as to why this would resolve the problem? Since these reports were updated from AR3, are the new components somehow loading previous printer settings? The issue I'm facing now is that we also have a Report Viewer form that has a Viewer control docked in it. If dlgPrint.ShowDialog() = DialogResult.OK Then Using dlgPrint As PrintDialog = New PrintDialog() Printer.PrinterSettings property to this PrintDialog.PrinterSettings object. I was able to resolve the issue for my client by showing a, and setting the section documents. 32Exception (0x80004005): The data is invalidĪt .GetHdevmodeInternal(String printer)Īt .GetHdevmodeInternal()Īt .GetHdevmode()Īt .get_PaperSource()Īt .(IntPtr hwndOwner)Īt .ShowDialog(IWin32Window owner)Īt .ShowDialog()Īt .Printing.PrintImpl.#zs(#q0B documentPrintAdapter, Action`1 action)Īt .(#q0B documentPrintAdapter, Boolean showPrintDialog, Boolean showPrintProgressDialog, Boolean usePrintingThread, Action`1 action)Īt .(DocumentModel documentModel, ReportModelBase reportModel, IApplicationContext context, Boolean showPrintDialog, Boolean showPrintProgressDialog, Boolean usePrintingThread)Īt .WindowsPrintService.Print(DocumentModel documentModel, ReportModelBase reportModel, IApplicationContext context, Boolean showPrintDialog, Boolean showPrintProgressDialog, Boolean usePrintingThread)Īt .Viewer.Print(Boolean showPrintDialog, Boolean showPrintProgressDialog, Boolean usePrintingThread)Īt .Viewer.Print(Boolean showPrintDialog, Boolean showPrintProgressDialog)Īt PM.ActiveReportsFunctions.PrintReportDocument(SectionDocument& sectionDocument, Boolean showPrintDialog, Boolean showPrintProgressDialog)Īt PM.AppointmentEditForm.PrintRoutingSlip() I understand that this may be a permissions issue, but didn't see any resolution for the thread started by someone else on a later version of AR ().Īny assistance would be greatly appreciated! None of these attempts have yielded positive results.
#Activereports 7 borderlinestyle code#
NET framework source code itself and tried to set the PrinterSettings property to null so it would instantiate a new PrinterSettings object dynamically. I have also tried setting the PrinterName property to null, and also to an empty string.
#Activereports 7 borderlinestyle windows#
I have uninstalled and re-installed the Windows XPS printer but that did not remedy the issue. They're trying to print to their default printer (Windows XPS) but the exception is thrown before the print dialog appears to make a printer selection. The user is logged in as an Administrator, and the issue still persists when the target application is invoked with Admin privileges.
#Activereports 7 borderlinestyle Pc#
The afflicted PC is on Win 7 Home, and we're making use of AR 8 SP3 (8.3.634.0). The same report prints correctly on other customers' systems as well. The same report prints without issue on other machines within this customers LAN. I have a customer who receives the exception below when attempting to print a section report. More information on the shape control is here.I'm having an issue with printing a report document that I could use some help with.

The code to use a shape would be similar to how I structured the code above, but you would set the Top/Left/Width/Height and the Visible property of the shape control instead of setting border properties. Just make sure the shape's z-order is under the textboxes. If a circle shape is important for you, you could use the "Shape" control in ActiveReports to do this by setting it's position and visibility based on a condition. You can calculate the position based on some things, but I would recommend using the control itself to highlight the data you want rather than drawing on the page. Getting the position of a control on the resulting page is not as easy. Read here for more info on the border property. For example, if you wanted to set the border of a textbox when its value is less than zero, you might use something like the following code: private void detail_Format(object sender, System.EventArgs eArgs)

You can turn on a border by setting the properties of the control in the Format event.
