Additional Address Lines on version 8

[Luvsql]

I am modifying the POP Blank Form on version 8 (deleted report in report writer, then re-inserted as errored during upgrade). I have modified the existing Vendor Address 1-3 within Calculated fields to add the Country (removing the last ""). I then create a vendor address 4,
which is identical to 1-3 except for a number 4 for the line number.

This is what I have done in all previous versions and it has worked fine. When I go to print I get an error "Max symbol length exceeded: Increase MAX_TOK_LEN." If I delete the new calculated field it prints fine. All our
SOP reports have the 4 line, but were upgraded to version 8. This is a new version 8.

Can we have 4 address lines on reports in version 8?

 

[winthropdc]

You have reached the maximum limit for the number of calculated fields on a report. If you can find another calculated field which you don't need, then you can remove it to make space. Maybe you can use the symbol that specifies that the line has already been printed.

David Musgrave [MSFT]
Senior Development Consultant
MBS Services - Asia Pacific

Microsoft Business Solutions

http://www.microsoft.com/BusinessSolutions

Any views contained within are my personal views and
not necessarily Microsoft Business Solutions policy.
This posting is provided "AS IS" with no warranties,
and confers no rights.

 

[Luvsql]

This is a standard report ie the POP Blank Form. We can't even add our own calculated fields onto a report? On version 7.5, I was able to do this without an issue.

 

[winthropdc]

Yes this is the standard report, but it has more functionality than the previous versions and so has more calculated fields. The problem is that the core functionality has used up most of the space for Calculated fields.

I will check with development if the limit can be increased in a future build of Dexterity and its runtime.

David Musgrave [MSFT]
Senior Development Consultant
MBS Services - Asia Pacific

Microsoft Business Solutions

http://www.microsoft.com/BusinessSolutions

Any views contained within are my personal views and
not necessarily Microsoft Business Solutions policy.
This posting is provided "AS IS" with no warranties,
and confers no rights.