List of changes for BW client: 7.6a.1 -------------------------------------------------------------------------------- DevMahler: # 23705 (BDNT16472): BwPrint Silent Test Document error messages Date: Fri, 29 Oct 2004 14:42:34 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) Some error were logged into EventViewer "SYSTEM" when printing any report. Details : First two messages are normal every time you print. If you print a Word doc you will receive these two messages. Event Type: Information Event Source: Print Event Category: None Event ID: 13 Date: 30-09-2004 Time: 14:48:31 User: NT AUTHORITY\SYSTEM Computer: SVAPPMG Description: Document 3, rttaad341001000 owned by baan was deleted on LJMG07-hp LaserJet 1300 PCL. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Information Event Source: Print Event Category: None Event ID: 10 Date: 30-09-2004 Time: 14:48:31 User: NT AUTHORITY\SYSTEM Computer: SVAPPMG Description: Document 3, rttaad341001000 owned by baan was printed on LJMG07-hp LaserJet 1300 PCL via port IP_192.168.2.17. Size in bytes: 19056; pages printed: 1 For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Information Event Source: Print Event Category: None Event ID: 10 Date: 30-09-2004 Time: 14:48:30 User: NT AUTHORITY\SYSTEM Computer: SVAPPMG Description: Document 2, BwPrint Silent Test Document owned by baan was printed on LJMG07-hp LaserJet 1300 PCL via port IP_192.168.2.17. Size in bytes: 0; pages printed: 0 For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Error Event Source: Print Event Category: None Event ID: 61 Date: 30-09-2004 Time: 14:48:30 User: SVAPPMG\baan Computer: SVAPPMG Description: The document BwPrint Silent Test Document owned by baan failed to print on printer LJMG07-hp LaserJet 1300 PCL. Win32 error code returned by the print processor: 259. No more data is available. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Error Event Source: Print Event Category: None Event ID: 45 Date: 30-09-2004 Time: 14:48:30 User: SVAPPMG\baan Computer: SVAPPMG Description: Document failed to print due to GDI/Driver error in rendering. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Workaround Ignore errors logged in Windows System Event Log. Test Procedure The modification is tested by the customer, who was able to reproduce this problem each time. We didn't succeed reproducing this problem internally, therefore testing internally was not possible. You can just print something to a printer, and check if no errors are logged in the Windows System Event Log. Affected Executables bwprint.exe Motive source DF:150593 -------------------------------------------------------------------------------- DevMahler: # 23611 (BDNT16403): TCS800-143458 Cannot add data to own created session Date: Wed, 20 Oct 2004 14:43:23 +0200 (CEST) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) Open test session: axvvv0101m000. No data is available yet in this table. Insert one record and fill this record. Tab to next record. Now the first record is blanked. Test Procedure See problem description. Problem can be reproduced with any Multi-occ maintain Session when the first record is empty. Affected Executables bw.exe Motive source TCS:800-143458 -------------------------------------------------------------------------------- DevMahler: # 23146 (BDNT16004): TCS800-137630 Not enough space for session titles in small dialogs Date: Tue, 17 Aug 2004 10:16:44 +0200 Created on: MaintNewton Type: bugfix Problem Description (Customer terms) General:Not enough space for session titles in small dialogs Examples: - Start session... - Error messages. Test Procedure Use test session: tewhrmess on system ping. Affected Executables bw.exe Motive source TCS:800-137630 -------------------------------------------------------------------------------- DevMahler: # 22741 (BDNT15675): BwPrint: reportname containing special characters Date: Wed, 23 Jun 2004 15:23:07 +0200 Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) The name of the report contains special characters like a-umlaut. Such a reportnames can be generates when running reports from Easy SQL. The Bwprint option header looks like: @ -p "" -c 3 -f 1 -t 999999 -l 66 -m 0 -L ISO-8859-1 -a 1 -r rwhsqlhäll -w 94 -d P "BW" -B "BW"@ Now when printing the report, the first line of the report contains the last part of the Bwprint option header: äll -w 94 -d P "BW" -B "BW"@ And then the report starts. Workaround Take care that the report name only contains ascii characters. Test Procedure Create a report with special characters in the name (with easy sql) and print it to bwprint. Affected Executables bwprint.exe Motive source DF:148191 -------------------------------------------------------------------------------- DevMahler: # 22730 (BDNT15674): Audio signal on message in BW Date: Wed, 23 Jun 2004 09:14:06 +0200 Created on: DevMahler Type: bugfix Problem Description (Customer terms) All standard Windows programs produce a sound when a Windows message box is diplayed. The sound type is set in the control pannel. However when this occurs in Baan Sessions this sound does not appear. Test Procedure Use any Baan Session and make sure a message is given. For instance: close session without saving. Affected Executables bw.exe -------------------------------------------------------------------------------- DevMahler: # 22629 (BDNT15461): Bwprint and Windows Server Printer (Silent Mode) modifications Date: Fri, 11 Jun 2004 14:47:52 +0200 Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) When using device type "Windows Server Printer" (server based printing), Bwprint does only print when the specified device is locally installed on the Baan server and shared for all users. It showed out that it is even necessary to be logged in at the Baan server as the same user who does the print job. This is a not workable situation. In case of server based printing, it should be not required to have printers installed on the Baan server. Workaround Have a the specified device installed on the Baan server and shared for all users. Test Procedure Run all kind of different scenarios when using Windows Server Printer device. For example: what happens when specifying an invalid device, what happens when having no printers at all at the Baan server etc. Refer also to Scopus solution 144291 for more info. Affected Executables bwprint.exe Motive source DF:145159 -------------------------------------------------------------------------------- DevMahler: # 22559 (BDNT15540): Allow DsNblockMode also in create window Date: Mon, 7 Jun 2004 12:15:24 +0200 Created on: MaintNewton Type: bugfix Problem Description (Customer terms) It has been agreed with the company Mercury to add a DsNblockMode attribute to the Main Window object and Pseudo Main Window object. Allow this object for Pseudo Main Window aswell and at creation time. Test Procedure Run LoadRunner scripts. Affected Executables bw.exe ------------------------------------------------------------------------------ DevMahler: # 22521 (BDNT15514): Ignore DsNblockMode attribute in BW Date: Thu, 3 Jun 2004 16:53:16 +0200 Created on: MaintNewton Type: bugfix Problem Description (Customer terms) It has been agreed with the company Mercury to add a DsNblockMode attribute to the Main Window object. This attribute will be set by the 4GL-Engine when the 4GL-Engine finishes processing an event. This allows the product LoadRunner to synchronize on the DS-protocol. Test Procedure Run LoadRunner scripts. Affected Executables bw.exe ------------------------------------------------------------------------------- DevMahler: # 22437 (BDNT15433): TCS800-140601 Selected text not removed by typing in a new text Date: Wed, 19 May 2004 16:13:05 +0200 Created on: DevMahler Type: bugfix Problem Description (Customer terms) Open a random session e.g. ttaad1520m000. Press ctrl+f. The problem is, that if the input field contains a string that's lenght equals of the maximum length of the input field, when the whole text is selected, a keypress should remove the whole content and replace with the pressed key. In this case: Max length is 8. Text is: 12345678. When the whole text is selected, and letter 'a' is pressed, this letter should appear and replace the original '12345678' string. But nothing happens. Test Procedure See problem description. Affected Executables bw.exe Motive source TCS:800-140601 -------------------------------------------------------------------------------- DevMahler: # 22429 (BDUX15425): shared memory not loaded message on Iseries Date: Wed, 19 May 2004 14:47:54 +0200 Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) "Shared memory not loaded or not accesible" message when customers wants to connect with BW to iSeries. Workaround Remove trailing / in .bwc file . Test Procedure See Problem Description Affected Executables all -------------------------------------------------------------------------------- DevMahler: # 22412 (BDNT15409): BW: where used table corrupted Date: Tue, 18 May 2004 10:33:18 +0200 Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) BW sometimes reports "duplicate key" errors. Affected Executables bw.exe Motive source DF:146928 -------------------------------------------------------------------------------- DevMahler: # 22375 (BDNT15382): TCS200-98316 Entry of 20 multi-byte characters in description field Date: Thu, 13 May 2004 11:07:06 +0200 Created on: MaintNewton Type: bugfix Problem Description (Customer terms) Usually, When I try to enter string into a input field, the max count is calculated by BW and we can not enter beyond the max count of character. But, At BW-7.4a or higher, the checking count is wrong. As result of it, before enter TAB, we can enter characters exceed the max limit. And when I enter TAB, the entered string is truncated. This problem happens when the multi-byte characters and single-byte characters are mixed in one filed. With B50c and BW-7.1d.xx, such things doesn't happen. With B50c and BW-7.4xxx, same problem happens. Test Procedure See problem description. Affected Executables bw.exe Motive source TCS:200-98316 --------------------------------------------------------------------------------