P38) Wrong Confirmation Message
Error
When choosing the deletion option for deleting a language when exporting a language module, the deletion option would not list all available languages with same name like for English.
This has been corrected
fin.exe
finsql.exe
P39) End Of Line Was Not Treated As White Space In XML
Error
When reading a xml file, the XMLPort did not treat the end of line as white space.
This has been corrected
P40) Internal Error 1 In Module 43
Error
When designing a report or data-port it was possible to create a “Data Item” with a name longer than 30 characters. Compile time this would lead to the error message: “Internal Error 1 in Module 43”. Now a warning message will appear when exceeding the allowed amount of characters.
This has been corrected
VSA reference: 8502141
P41) Not Possible To Use Dimension Filter In Dataports
Error
It is now possible to use a dimension filter in dataports.
This has been corrected
VSA reference: 8448443
P42) References To Non-Existing Tables Could Make Navision Crash
Error
Navision could crash if a table field was referring to another table and the other table was non-existing.
This has been corrected
Clarify reference: SRZ060125001144
P43) Buffer Over Run When Using Copy Function In Code Units
Error
A buffer overrun could occur if you used the copy function CTRL + C and scrolled to the end of the code unit.
This has been corrected
P44) SHELL Parameter Too Short
Error
The SHELL parameter was limited to 80 characters. Now the variable length is 256.
This has been corrected
VSA reference: 8363740
P45) Menu Suite Design
Error
When designing a menu suite with more levels and removing a level in the middle could cause a crash when trying to design a level below the removed level.
This has been corrected
P46) Not Possible To Have 20 Character Fields In Streams
Error
When using STREAM.WRITE with a 20 character field and creating a STREAM.READ for the same field could cause an overflow error.
This has been corrected
P47) Auto Positioning Does Not Work
Error
When the navigation pane was hidden the auto positioning of forms worked correctly, but when the navigation pane was visible auto positioning did not work when several forms were opened.
This has been corrected
P48) Not Possible To Design Form
Error
It was possible to create C/AL code on a form trigger that could run fine but it was not possible to design the form after the code was implemented.
This has been corrected
Issues
P49) Visual Studio 2005
Issue
It was not possible to look up “Ntimer” and “Navision Socket Bus Adaptor” from Visual Studio 2005.
This has been corrected
P50) Maximum And Minimize Buttons Missing
Error
The “field look up” window in XML port Designer did not have the maximum and minimize buttons.
This has been corrected
P51) XML Port Can Not Interpret Tabs
Error
If an element in a XML document included much tabulation it could cause a crash.
This has been corrected
VSA reference: 8452854
P52) XML Version Numbering Not Working
Error
It was not possible to change the version number for XML documents created by a XML Port.
This has been corrected
VSA reference: 8085070
P53) Not Possible To Assign Table Fields Before Table Relation
Error
When designing a XML port it was not possible to assign a table field before assigning a table reference.
This has been corrected
P54) XML Ports Can Be Created Without Defining Tags
Error
It was possible to create a XML Port without defining any tags and it could cause a crash when trying to use the XML Port.
This has been corrected
P55) XML Ports Can Not Import Documents With Mixed Content
Error
It was possible to create a XML Port that could export XML documents with mixed element content. It was not possible import XML documents with mixed element content. Now both import and export of XML documents with mixed element content is allowed.
Уважаемый посетитель!
Чтобы распечатать файл, скачайте его (в формате Word).
Ссылка на скачивание - внизу страницы.