Bugfixes BwPrint.exe version 7.1d.02 / PA.2231
==============================================
MaintCorelli: # 17649 (BDNT11109): Bwprint: log usefule error in case barcode image cannot be generated

Date: Thu, 20 Mar 2003 16:24:21 +0100

Created on:  MaintBaanIVc
Type:        bugfix

Problem Description (Customer terms)
When a barcode is not specified correctly, e.g. wrong barcode length, bwprint just does not show or print
the barcode image. It is a hard time to figure out what the reason is. Therefore a useful error would be nice.

Workaround
Check out the contents of the bpf file for the control codes representing the barcode.

Test Procedure
Specify a barcode in a report which specifications are not according the "rules" of that barcode.
And print this report to a Windows printer device. Bwprint should log an error in that case.
You can also do the Barcode test in bwprint, and save this test as another file, modify the file manually, 
so it contains wrong specified barcodes.

Affected Executables
bwprint.exe

Motive source
DF:135037

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

MaintCorelli: # 17587 (BDNT11017): Bwprint: add option to use default printer automatically

Date: Fri, 14 Mar 2003 14:47:44 +0100

Created on:  MaintBaanIVc
Type:        bugfix

Problem Description (Customer terms)
When running nightly jobs (in the background), sometimes it can happen that a job does not continue to run, because bwprint cannot find the specified printer. At that moment bwprint pops up the message: Printer '<name of the specified printer>' not found, print to default printer?. Because the printsession is running in a job this question is not being be answered. It should be possible to specify that bwprint will use automatically the default windows printer, without asking.

Workaround
Do not run bwprint.exe in the background, or take care that the specified printer is available.

Test Procedure
The following device is defined in Baan (ttaad3100m000 Device Data):

Device Type: Windows Printer
Device Queue: \\cnl08696\blablabla
Paper Type: A4
Page Length: 66

On my local pc, cnl08696 device "blablabla" does not exists.
Print from a voluntary printsession to this device. (Do not check "Preview" option).

When printing from Baan to this device,  by default behaviour bwprint asks me:
Printer '\\cnl08696\blablabla' not found, print to default printer?
After pressing OK, the default printer is used.

Now, start bwprint (by doubleclicking bwprint.exe), and select Fonttest from the Help.
Right click on some text and select "Default Printer" from the drop down menu.
Then select "Enable automatic use of default printer"

Print again from a voluntary print session from Baan, using the same device.
Now, bwprint should not ask you to print to the default printer, but should automatically use the default printer.

Now, start bwprint (by doubleclicking bwprint.exe), and select Fonttest from the Help.
Right click on some text and select "Default Printer" from the drop down menu.
Then select "Disable automatic use of default printer (default)"

Print again from a voluntary print session from Baan, using the same device.
Now, bwprint should ask you to print to the default printer, and should not automatically use the default printer.

Affected Executables
bwprint.exe

Motive source
DF:133429

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

MaintCorelli: # 17171 (BDNT10287): Remove warning Language DLL not found

Date: Wed, 12 Feb 2003 13:59:10 +0100

Created on:  MaintCorelli
Type:        bugfix

Problem Description (Customer terms)
The Event Log of Windows contains a lot of Warnings like:

Language DLL resBWj0.dll not found in directory C:\Program Files\Baan\fcbaan5c\bin\res, taking default (English) language

Because of this Warnings real errors are more difficult to find.


Workaround
Refer to scopus solution 120944

Test Procedure
Have for example a non-english BaanERP environment.
Eg. Japanese.
Log on to this environment.
No warning like described in the Problem Description should be logged.

Affected Executables
bshell, bw, bwprint, etc

Motive source
DF:120944

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