Regarding [] and 2.x reports
We see many complains about broken reports when upgrading to 3.16. The main
reason is that 3.16 allows to use [ ] instead of < > (2.x reports style). It
was introduced to simplify the migration of old reports. Now we prepare the
conversion utility that allows to open .frf files "on the fly". All you need
is to include "frx2xto30.pas" unit into your uses list (in any place in your
project). This utility performs the following:
- allows open .frf files in designer and in code:
frxReport1.LoadFromFile('file.frf')
- modifies the PascalScript syntax to allow using [ ] instead of < >
- modifies the PascalScript syntax to allow using non-declared variables
- allows use [Table1."Field1"], where Table1 is of TDataset type (in FR3
Table1 should be TfrxDBDataset)
- some other 2->3 compatibility issues
If you don't use this utility, you will not able to use [ ] - all things
will works as in FR3.15 (including use of script variables inside < >).
reason is that 3.16 allows to use [ ] instead of < > (2.x reports style). It
was introduced to simplify the migration of old reports. Now we prepare the
conversion utility that allows to open .frf files "on the fly". All you need
is to include "frx2xto30.pas" unit into your uses list (in any place in your
project). This utility performs the following:
- allows open .frf files in designer and in code:
frxReport1.LoadFromFile('file.frf')
- modifies the PascalScript syntax to allow using [ ] instead of < >
- modifies the PascalScript syntax to allow using non-declared variables
- allows use [Table1."Field1"], where Table1 is of TDataset type (in FR3
Table1 should be TfrxDBDataset)
- some other 2->3 compatibility issues
If you don't use this utility, you will not able to use [ ] - all things
will works as in FR3.15 (including use of script variables inside < >).