Untill now I genererated reports that contain global cfs. That works fine, but my users are not allways happy with the rigid text and rigid layout of the reports and asked for excel files which they can use for Word/OpenOffice merge actions.
I noticed some threads about exporting calculated fields (to excel). They are a bit old, so I wonder if, maybe in V7, the way to export calculated fields has changed.
I am a bit confused about calculated fields. As far as I understand, there are calculted fields that you can define in Field Rules. Those fields are stored in the table and you can read out the value any time.
Next to that, there are the global calculated fields (cfs). As far as I understand, you don't find those fields in the table structure. This feature is used for reports, letters, forms and so on.
In the WAS environment I found that Field Rules cfs can appear in grids, and
Global cfs cannot. This means that in he WAS environment you have tot define the global cfs in every grid where you want to use them. This leads to the conclusion that, when you build a web app, it is smarter to define Field Rules cfs, despite the extra table space that is generated.
Is this assumption correct?
Now for the export: I tried to use the described 'export' table in order to make the global cfs 'physical' after which they are 'exportable'. This did not work. Probably I do something wrong.
Is there in V7 a way to get this done in a more dummy way?
Thanks,
Ren�
I noticed some threads about exporting calculated fields (to excel). They are a bit old, so I wonder if, maybe in V7, the way to export calculated fields has changed.
I am a bit confused about calculated fields. As far as I understand, there are calculted fields that you can define in Field Rules. Those fields are stored in the table and you can read out the value any time.
Next to that, there are the global calculated fields (cfs). As far as I understand, you don't find those fields in the table structure. This feature is used for reports, letters, forms and so on.
In the WAS environment I found that Field Rules cfs can appear in grids, and
Global cfs cannot. This means that in he WAS environment you have tot define the global cfs in every grid where you want to use them. This leads to the conclusion that, when you build a web app, it is smarter to define Field Rules cfs, despite the extra table space that is generated.
Is this assumption correct?
Now for the export: I tried to use the described 'export' table in order to make the global cfs 'physical' after which they are 'exportable'. This did not work. Probably I do something wrong.
Is there in V7 a way to get this done in a more dummy way?
Thanks,
Ren�