Adam, thanks for sharing this. It's a great trick to make this work,
even if it doesn't work in all contexts.
I myself have used the Logicity viewer to view from Vantage some of my
custom ODBC reports. I created a custom BOM report, and found that the
Crystal Reports runtime in Vantage produces wacky results if you use
lots of subreports.
I would develop the report, and it would look fine in the CR runtime
inside Crystal Reports. When I went to run it in Vantage, it would run,
but some fields in the subreports would be randomly blank.
After a lot of headscratching I tried a different CR runtime, and the
Logicity one worked perfectly! So I wrote a little bit of scripting
framework that lets me check to see if the user has the necessary
prerequisites installed (Logicity Viewer and SQL Native Client). If so
it launches the Logicity viewer, if not it points them at a web page
where they can get the prereqs.
-bws
--
Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
Picometrix
bspolarich@... ~ 734-864-5618 ~
www.advancedphotonix.com
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of aelinuxguy
Sent: Wednesday, January 14, 2009 8:27 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: 8.03.4XX Print when clicking a Button
--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , "Vic
Drecchio" <vic.drecchio@...> wrote:
I attempted to reply to this earlier, but my message never showed up.
In any case, if you got this message before I apologize in advance.
I had this same request at one point and came to the same conclusion
as Vic. However, I did find a work around solution that I wanted to
share with the group. Full disclosure here, my company wrote the
third party software involved in this solution. I am posting this
only as a solution to the problem and not as marketing for the
product. Anyway, the work-around I came up with was to use the third
party Crystal Reports viewer Logicity and make use of a feature called
command line replacements in the Pro version. I can e-mail each of
the components to this solution if that would help, but here is the
executive summary for a pallet tag that printed on the receipt to
inventory screen:
1. Write a regular Crystal Report directly connected to the database
via ODBC with parameters for the screen fields you'd want to pass into
the report to give you context-specific data.
2. Using Logicity Solution Builder, create a solution file and
specify a variable name of your choice for the parameters on the
report. I used %JOB_NUMBER% for the 'Job Number' parameter.
3. Logicity Desktop can be invoked to fire off this solution file
and, at runtime, replace the variables you defined with values. We
utilize this feature to build a dynamic command line string from the
customization. Here is the relevant section from my customization:
Private Sub btnEpiCustom1_MouseDown(ByVal Sender As Object, ByVal
Args As System.Windows.Forms.MouseEventArgs) Handles
btnEpiCustom1.MouseDown
Dim edv As EpiDataView =
CType(oTrans.EpiDataViews("PartTran"), EpiDataView)
Dim JobNum as string = edv.dataView(edv.row)("JobNum")
Process.Start("C:\Program Files\SaberLogic\Logicity\Logicity
Desktop.exe", "P:\Projects\Reports\PalletTags.rrd JOB_NUMBER=" & JobNum)
End Sub
Like I said, if anybody wants each of the components of this solution
to review in more detail, e-mail me and I can send them to you directly.
Hope this helps,
[Non-text portions of this message have been removed]
even if it doesn't work in all contexts.
I myself have used the Logicity viewer to view from Vantage some of my
custom ODBC reports. I created a custom BOM report, and found that the
Crystal Reports runtime in Vantage produces wacky results if you use
lots of subreports.
I would develop the report, and it would look fine in the CR runtime
inside Crystal Reports. When I went to run it in Vantage, it would run,
but some fields in the subreports would be randomly blank.
After a lot of headscratching I tried a different CR runtime, and the
Logicity one worked perfectly! So I wrote a little bit of scripting
framework that lets me check to see if the user has the necessary
prerequisites installed (Logicity Viewer and SQL Native Client). If so
it launches the Logicity viewer, if not it points them at a web page
where they can get the prereqs.
-bws
--
Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
Picometrix
bspolarich@... ~ 734-864-5618 ~
www.advancedphotonix.com
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of aelinuxguy
Sent: Wednesday, January 14, 2009 8:27 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: 8.03.4XX Print when clicking a Button
--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , "Vic
Drecchio" <vic.drecchio@...> wrote:
>the future in Vantage.
> No, unfortunately. I'd love to see in-context reports as a thing of
>BAQ report/Crystal Report.
> Without the SDK, I know no way to pass the current "whatever" to the
I attempted to reply to this earlier, but my message never showed up.
In any case, if you got this message before I apologize in advance.
I had this same request at one point and came to the same conclusion
as Vic. However, I did find a work around solution that I wanted to
share with the group. Full disclosure here, my company wrote the
third party software involved in this solution. I am posting this
only as a solution to the problem and not as marketing for the
product. Anyway, the work-around I came up with was to use the third
party Crystal Reports viewer Logicity and make use of a feature called
command line replacements in the Pro version. I can e-mail each of
the components to this solution if that would help, but here is the
executive summary for a pallet tag that printed on the receipt to
inventory screen:
1. Write a regular Crystal Report directly connected to the database
via ODBC with parameters for the screen fields you'd want to pass into
the report to give you context-specific data.
2. Using Logicity Solution Builder, create a solution file and
specify a variable name of your choice for the parameters on the
report. I used %JOB_NUMBER% for the 'Job Number' parameter.
3. Logicity Desktop can be invoked to fire off this solution file
and, at runtime, replace the variables you defined with values. We
utilize this feature to build a dynamic command line string from the
customization. Here is the relevant section from my customization:
Private Sub btnEpiCustom1_MouseDown(ByVal Sender As Object, ByVal
Args As System.Windows.Forms.MouseEventArgs) Handles
btnEpiCustom1.MouseDown
Dim edv As EpiDataView =
CType(oTrans.EpiDataViews("PartTran"), EpiDataView)
Dim JobNum as string = edv.dataView(edv.row)("JobNum")
Process.Start("C:\Program Files\SaberLogic\Logicity\Logicity
Desktop.exe", "P:\Projects\Reports\PalletTags.rrd JOB_NUMBER=" & JobNum)
End Sub
Like I said, if anybody wants each of the components of this solution
to review in more detail, e-mail me and I can send them to you directly.
Hope this helps,
[Non-text portions of this message have been removed]