List of changes for BW 7.1d.08.161, BWPRINT 7.1d.08 (PA.2680) ------------------------------------------------------------------------------- MaintCorelli: # 24227 (BDNT16959): Vertical lines are interrupted in bwprint Date: Wed, 5 Jan 2005 11:12:35 +0100 (CET) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) Merge of BDNT16694. Workaround n/a Test Procedure see BDNT16694 Affected Executables bwprint.exe Motive source DF:151495 -------------------------------------------------------------------------------- MaintCorelli: # 24019 (BDNT16626): Gray not printed in BwPrint Date: Mon, 13 Dec 2004 10:08:46 +0100 (CET) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) Report fields defined to be printed in gray (light gray or dark gray) are printed through bwprint in black. Workaround N/A Test Procedure Create one or more fields on a report and use the color gray for these fields. In BW print the report using 'preview'. The field defined in gray should be displayed in gray. Affected Executables bwprint.exe Motive source DF:151481 -------------------------------------------------------------------------------- MaintCorelli: # 23909 (BDNT16673): DF151410 Creating new bwc file does not create a new dcom object Date: Wed, 24 Nov 2004 14:34:09 +0100 (CET) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) DCOM objects are not created in BECS. When creating a new connection in BECS after installation, DCOM object is only created the first time (when appears). When adding other .bwc files the new connections are not created anymore. Affected Executables bwc.dll Motive source DF:151410 -------------------------------------------------------------------------------- MaintCorelli: # 23777 (BDNT16481): BW: re-use of password information Date: Wed, 10 Nov 2004 09:45:23 +0100 (CET) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) A night, jobs are ran to extract data from the ERP Database. The first thing the batch job does, is logging on to the ERP database with a fixed logon and password. That logon and password is saved in the BWC file on the server. For an unknown reason, the batch process stops and asks a password. The result is that a crucial Datawarehouse process waits on a user intervention, where is should run automatically. Workaround Fill in the password in the password dialog. Test Procedure I cannot specify a test procedure because I do not know how you can control Windows to return an username in uppercase. This is tested by the customer, and solved the problem. Affected Executables bwc.dll Motive source DF151440 -------------------------------------------------------------------------------- MaintCorelli: # 23701 (BDNT16472): BwPrint Silent Test Document error messages Date: Fri, 29 Oct 2004 14:42:12 +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 --------------------------------------------------------------------------------