List of changes for BW client:: 7.6a.01.3
-------------------------------------------------------------------------------

DevMahler: # 24562 (BDNT17231): Bwprint: Incorrect behavior in case of unknown device.

Date: Wed, 2 Feb 2005 13:45:05 +0100 (CET)

Created on:  MaintBaanIVc
Type:        bugfix

Problem Description (Customer terms)
When the printjob was generated with a device having an unknown printer, and the option "Preview" active.
If the option "Preview" is not active a message is shown "invalid print, print to default printer?"
But in preview mode the report is shown in bwprint, and it should be possible to select a printer.
But the options [print/print preview/print setup] do not work. This problem occured for the first time in 6.1c.07.06 version.

Workaround
Take care specified printer is a valid one.

Test Procedure
Create a Device (ttaad3100m000) of Type Windows Printer.
In the field "Device Queue" fill in "this printer does not exist"
Print using this device, and select "Preview" option.
When Bwprint is started, press the Print button.
Now it should show you a (default) printer of your Windows print setup, 
which you can use to print.


Affected Executables
Bwprint

Motive source
DF:153478

--------------------------------------------------------------------------------

DevMahler: # 24231 (BDNT16959): Vertical lines are interrupted in bwprint

Date: Wed, 5 Jan 2005 11:12:58 +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

--------------------------------------------------------------------------------

DevMahler: # 24023 (BDNT16626): Gray not printed in BwPrint

Date: Mon, 13 Dec 2004 10:09:26 +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

--------------------------------------------------------------------------------

DevMahler: # 23983 (BDNT16751): Make sure Reger and higher version BW can coexist with Unicode Corelli BW (bwconfig compatibility)

Date: Mon, 6 Dec 2004 08:36:48 +0100 (CET)

Created on:  MaintReger
Type:        bugfix

Problem Description (Customer terms)
With the Unicode variant of BW a new property is added to the bwc.dll.
Because this component is shared between all versions of BW, it must be assured the applied
changes are also available in Reger and higher version of BW.

Test Procedure
Install Reger or higher version of BW next to Unicode Corelli version of BW.

Affected Executables
bwc.dll
--------------------------------------------------------------------------------

DevMahler: # 23913 (BDNT16673): DF151410 Creating new bwc file does not create a new dcom object

Date: Wed, 24 Nov 2004 14:34:27 +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 <empty> appears). When adding other .bwc files the new connections are not 
created anymore.

Affected Executables
bwc.dll

Motive source
DF:151410
--------------------------------------------------------------------------------

DevMahler: # 23781 (BDNT16481): BW: re-use of password information

Date: Wed, 10 Nov 2004 09:45:53 +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
--------------------------------------------------------------------------------