Corey
10-May-2005, 10:45 PM
Just thought I would add my two cents worth as well with another method
without needing the dll, it's quick and easy and works.
Using Vs 9 CRW
- Add the CODEMAST to your report (database expert)
- Add an alias to the report for each additional field that you need the
codemast data for
- Link the specific table code field in your table to the codemast table
code field
Remember to use a left outer join view if you intend on allowing blanks
- As part of the selection criteria select the specific linked codemast
table or alias and set the codemast type.
This works for quick solution.
Corey
A Paul Anthony wrote:
> Last time I checked there was no entirely satisfactory way of using CodeMast
> to convert a code to its associated description ("RE: Display CodeMast Table
> Description in Crystal", Leslis Brennan, 21/10/2003). There was function,
> but it didn't work properly (and not just for me), so the general consensus
> was to add an extra field into the database with a fixed string as
> Codemast's type value. Which I did.
>
> I now have a better solution. If anyone's intested. :-)
>
> Create a subreport that simpley returns CodeMast.Description
> Import this to your main report
> Create a formula with the literal string of your codemast type value (I call
> the formula by the same string)
> Link your code field and formula to the subreport using parameters.
>
> I agree it's not ideal, but seems neater than changing the database field
> structure.
>
> A Paul Anthony
>
without needing the dll, it's quick and easy and works.
Using Vs 9 CRW
- Add the CODEMAST to your report (database expert)
- Add an alias to the report for each additional field that you need the
codemast data for
- Link the specific table code field in your table to the codemast table
code field
Remember to use a left outer join view if you intend on allowing blanks
- As part of the selection criteria select the specific linked codemast
table or alias and set the codemast type.
This works for quick solution.
Corey
A Paul Anthony wrote:
> Last time I checked there was no entirely satisfactory way of using CodeMast
> to convert a code to its associated description ("RE: Display CodeMast Table
> Description in Crystal", Leslis Brennan, 21/10/2003). There was function,
> but it didn't work properly (and not just for me), so the general consensus
> was to add an extra field into the database with a fixed string as
> Codemast's type value. Which I did.
>
> I now have a better solution. If anyone's intested. :-)
>
> Create a subreport that simpley returns CodeMast.Description
> Import this to your main report
> Create a formula with the literal string of your codemast type value (I call
> the formula by the same string)
> Link your code field and formula to the subreport using parameters.
>
> I agree it's not ideal, but seems neater than changing the database field
> structure.
>
> A Paul Anthony
>