У меня 8 студия от Component One
У меня тоже вылизали кроказябры избавился от них просто
В пакете студии идет тулса Report Designer – она представляет собой конструктор отчетов
на выходе из которого получается xml файл
так вот нужно чтоб по умолчанию в Report Properties Font был Arial Unicode MS
(в тексбоксах или лейблах можно ставить уже любой шрифт)
В xml файле вот этот тег:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
- <Layout>
<Width> 10170 </Width>
<MarginLeft> 1000 </MarginLeft>
<MarginTop> 800 </MarginTop>
<MarginRight> 1000 </MarginRight>
<MarginBottom> 800 </MarginBottom>
<Orientation> 1 </Orientation>
-</Layout>
-<Font>
<Name>Arial Unicode MS</Name>
<Size> 12 </Size>
-</Font>
vsprt7.ocx –не знаю, но догадываюсь что это типа vsrpt8.ocx
vsrpt8.ocx – размещается на форме (в рантайме его невидно) и методом лоад в него загружается указанный отчет
короче лучше код приведу:
1.
2.
3.
Start.VSReport1.Load VB.App.Path & "\Reports\1\Договор.xml", "rsBoxSource"
Start.VSReport1.DataSource.RecordSource = "Select *, rsBoxSource.код_договора from rsBoxSource WHERE rsBoxSource." & rsBoxSource.Filter
Start.VSReport1.Fields("Subreport").Subreport.DataSource.RecordSource = "Select *, rsEdit_DocG3.код_договор from rsEdit_DocG3 WHERE rsEdit_DocG3.код_договор=" & rsBoxSource("код_договора")
Start.VSReport1.Render VSPrinter1
vsprint7 – предназначен для отображения на форме загруженного файла из VSReport1(vsrpt8)
Вот вам из хелпа:
VSReport8 Control
The VSReport8 control is an invisible control that reads report definitions stored in XML files, combines them with data from ADO recordsets and generates reports that can be previewed, printed or saved to files. The control can export reports in HTML, DHTML, PDF and Text file formats, and in a form usable by the VSPrinter8 control. The control can be distributed royalty-free with your applications.
The control uses an object model largely based on Microsoft Access reports, and it supports most features found in Access reports, including:
1. A Microsoft Access-style banded-report model based on Groups, Sections, and Fields. (These objects are fully exposed by the object model, so you can write your own report designers.)
2. Fields may be bound to simple and binary (object) database fields.
3. Fields may contain VBScript expressions, including extensions for aggregate expressions (Sum, Max, Average, etc.), and have access to the control's object model.
4. Reports may contain event handlers, making them independent of the host application.
5. Reports may contain Subreports.
6. Reports may contain parameterized queries, allowing the user to constrain the data that should be included in the report.
7. Report definitions may be saved within the control at design time, or loaded at run time from XML report definition files.
VSPrinter8 Control
The VSPrinter8 control provides VSReport8 with printing and previewing capabilities. It can be used to create documents without VSReport8, and has a rich feature set of its own.
To preview a report, you need both controls. VSReport8 reads data from a database and formats it according to the report definition, then sends its output to the VSPrinter8 control.
If you only want to create reports and save them into HTML or PDF files, you do not need to use a visible instance of the VSPrinter control on your form. However, VSReport8 uses VSPrinter internally, so VSPrinter needs to be installed and registered on the user's computer even if you are not using a visible instance of it. The control can be distributed royalty-free with your applications.
