Changes Made in Microsoft Business Solutions–Navision W1 4.0 SP3. Table of Content. Development Environment and Database Changes, страница 18

This has been corrected

dbd.dll

ndbcs.dll

VSA reference: 8276373

P22)  Synchronization Of Windows Login MS SQL 2005

Error

When synchronizing users between Microsoft Dynamics NAV and MS SQL 2005 could cause a hang for an undefined amount of time.

This has been corrected

P23)  SETVIEW Not Working For FILTERGROUPS

Error

SETVIEW would reset filter groups to zero. Filter groups would only work with SETRANGE.

Now FILTERGROUP works with SETVIEW on SQL-Server.

This has been corrected

VSA reference: 8399011, 8031757

P24)  Permission Error MS SQL 2005

Error

It was not possible to READ/WRITE data if the user was not registered in the database owner role.

This has been corrected

VSA reference: 8586483, 8569704, 8379257, 8492744

P25)  Error When Renaming Records

Error

Renaming a record with FLOWFIELDS would cause the FLOWFIELDS to show wrong amounts if the SIFT index was depending on closing dates. The problem would happen when updating the SIFT records for related records. Then "Closing Date" would be lost in the SIFT tables.

This has been corrected

VSA reference: 8450884

KB article reference: 919116

P26)  Navision Could Crash On Citrix Installations During Printing

Error

Navision could crash when trying to print from an installation on Citrix Presentation Server.

This has been corrected

P27)  Navision Could Crash When Moving Mouse On CITRIX Installations

Error

When moving the mouse cursor from a Navision window to the menu could cause a crash when running Navision in a CITRIX installation.

This has been corrected

VSA reference: 8421366

P28)  Certain Local Characters Are Not Recognized

Error

When using Windows login and you assign a user restriction for the Navigation Pane (example for the User Name Domain\Müllermitß then name appears as Domain\M³LLERMIT).

This has been corrected

VSA reference: 8340031

P29)  Database Owner Can Not Synchronize Permissions

Error

It was not possible to create a SUPER user login and synchronize permissions when creating a new database. An error message was thrown.

This has been corrected

VSA reference: 8278730 & 8331306

P30)  Long Login Time With Windows Logins

Error

When assigning several windows logins and creating multiple companies performance for windows logins was increased.

This has been corrected

VSA reference: 8397615

P31)  No Read Permissions On MS SQL 2005

Error

If a user was not system administrator on MS SQL Server 2005, it was not possible to create a user with READ permissions in Microsoft Dynamics NAV.

This has been corrected

VSA reference: 8379257

P32)  Transaction Log File Is Size Restricted With MS SQL 2005

Error

It was not possible to create a new database and define MAX_SIZE for the transaction log on MS SQL Server 2005.

This has been corrected

2.3  Development Environment

Errors fixed

P33)  XML Port Crashes

Error

It was possible create a “Field Data Source” before a “Table Data Source” which would lead to a crash when compiling the objects.

This has been corrected

Fin.stx

P34)  Wrong X-Coordinates

Error

The x-coordinates at forms could be larger than the today limited size at 100.000. Therefore this limit is increased to 400.000.

This has been corrected

P35)  Too Large Text In Reports Will Cause An Error

Error

If a text in a report where the size was larger than 1024, the user would receive an exception.

This has been corrected

P36)  Code Coverage Not Included in Debugger

Error

It was not possible to use the code coverage tool from the debugger.

This has been corrected

fin.exe

finsql.exe

cfront.dll

VSA reference: 8387483

P37)  Leaks In XML Ports.

Error

There were some misinterpretation in the old XML port code. This has been corrected to prevent leaks.

This has been corrected

fin.exe

finsql.exe

nas.exe

nassql.exe