Dick,
I've pasted an old email below, which is how I did this for the POForm. Perhaps you could translate it for the SO Pick List as well.
Troy Funte
Liberty Electronics
-----Instructions Begin Here--------------
Here's how I added a field from a table that was not included in a Crystal Canned report. I linked via ODBC, so each machine that runs the report will need to have ODBC installed.
The problem with linking comes with the fact that ALL fields are converted to Strings in the .dbf tables that are created for the canned report. Whereas, the key field I was working with in PORel was a numeric field. With Crystal, you can link to a formula through a subreport. So, you create a formula in the main report which converts the Key String Field to a Number. In Crystal 8 this is the ToNumber(x) function, where x is the string.
So your formula would simply be named, for instance "PO#," and the formula would be "ToNumber({PORel.PONum})"
This formula, PO#, is what is linked to PORel.PONum in your subreport. Then you can share variables across reports, or simply have the field you're looking for in your subreport and place the subreport in the appropriate spot in your main report. If you use the subreport field in a formula in the main report, you will need to use a shared variable. This gets a little more complicated because of the timing of processing subreports, but is possible.
Hope this helps, and contact me if you have more questions
---------- Instructions End Here ------------
I've pasted an old email below, which is how I did this for the POForm. Perhaps you could translate it for the SO Pick List as well.
Troy Funte
Liberty Electronics
-----Instructions Begin Here--------------
Here's how I added a field from a table that was not included in a Crystal Canned report. I linked via ODBC, so each machine that runs the report will need to have ODBC installed.
The problem with linking comes with the fact that ALL fields are converted to Strings in the .dbf tables that are created for the canned report. Whereas, the key field I was working with in PORel was a numeric field. With Crystal, you can link to a formula through a subreport. So, you create a formula in the main report which converts the Key String Field to a Number. In Crystal 8 this is the ToNumber(x) function, where x is the string.
So your formula would simply be named, for instance "PO#," and the formula would be "ToNumber({PORel.PONum})"
This formula, PO#, is what is linked to PORel.PONum in your subreport. Then you can share variables across reports, or simply have the field you're looking for in your subreport and place the subreport in the appropriate spot in your main report. If you use the subreport field in a formula in the main report, you will need to use a shared variable. This gets a little more complicated because of the timing of processing subreports, but is possible.
Hope this helps, and contact me if you have more questions
---------- Instructions End Here ------------
----- Original Message -----
From: PLAMAN DICK
To: 'vantage@yahoogroups.com'
Sent: Thursday, August 23, 2001 9:07 AM
Subject: [Vantage] SO Pick List
Fellow Vantageers,
We currently are on Vantage Vintage 4.904.
I would like to modify the Crystal Reports (8.5) version of the
SO Pick List to add the lot number. Alas, this field
is not in the selection list, and when I attempt to try
to add the part-bin table and link to the tables already
linked, I get errors.
Has anyone overcome this problem or tell me
where I am going wrong?
Thanks in advance.
Yahoo! Groups Sponsor
Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and Crystal Reports and other 'goodies', please goto: http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto: http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto: http://groups.yahoo.com/group/vantage/links
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Non-text portions of this message have been removed]