Bugfixes BwPrint.exe version 7.1c.03

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

MaintCorelli: # 13048 (BDNT6732): BwPrint: Does not recognize locally (shared) printer

Date: Tue, 22 Jan 2002 09:40:42 +0100

Created on:  MaintBaanIVc
Type:        bugfix

Problem Description (Customer terms)
Locally installed printer on LPT1 are not recognized anymore after upgrading from BW 57 to BW 62
Install a printer on port LPT1 and share it.
Create a device of type windows printer and fill in the URL in the device queue.
Bwprint will not recognize the locally installed printer. 
Instead it will ask at every printout to install the printer locally YES/NO.

Problem Description (Technical terms)
This problem is introduced by bugf_BDNT5175. A check is built in if a printer is locally installed.
But in case the sharename of a printer is used, which is locally shared, the baanDeviceName differs from the 
lpInfo->pPrinterName.
Because lpInfo->pPrinterName contains the real printername, and not the sharename.
Therefor "found" is set to FALSE, although the printer exists locally.
So, the test should also check using the lpInfo->pShareName, which contains the sharename of the printer.

Workaround
Use the real name of the printer instead of the share name.

Test Procedure
Have a printer locally installed, and share this printer.
Print to this printer using its sharename.
Bwprint should not ask you to install this printer.

Eg.
Printer locally installed = HP DeskJet 540
Share name of this printer = deskjet
System name = cnl08168

Now, the field "Device Queue" of the Windows Printer Baan device should contain the following:
\\cnl08168\deskjet

(Also tests done using locally installed network printers, local printers, and using ip addresses in 
stead of hostnames)

Affected Executables
bwprint.exe

Scopus defectnumber(s)	Scopus casenumber(s)	Priority (e.g. 10)
119706			650049			20
			641882
			651007



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

MaintCorelli: # 12535 (BDNT6588): Error message bse_tmp only to log as a warning

Date: Tue, 11 Dec 2001 14:30:40 +0100

Created on:  MaintBaanIVc
Type:        bugfix

Problem Description (Customer terms)
In case BSE_TMP directory is not accessable an error message is popping up in the BW Message Box.
The same error is also logged in the Event Log as a stopping error.
Because this error is only information, we don't like popping up each time this error in the
BW Message Box.

Problem Description (Technical terms)
Error logged with attribute TO_SET.

Workaround
not applicable

Test Procedure
Run BW from a read-only network share, and print something using a Windows Printer.
Only a warning should be logged in the Windows Event Log, like:

Message	 c:\program files\baan\baanivc test\tmp: not accessable; defaulting to TEMP directory

Affected Executables
bw.exe, bwprint.exe, and others

Scopus defectnumber(s)	Scopus casenumber(s)	Priority (e.g. 10)
120149						30



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

MaintCorelli: # 12308 (BDNT6364): Extra modification for project VHNT6328

Date: Mon, 5 Nov 2001 12:14:54 +0100

Created on:  MaintBaanIVc
Type:        bugfix

Problem Description (Customer terms)
Project VHNT6328 didn't fix problem completely correct.

Problem Description (Technical terms)
Wrong flag specified for CreateFile, and ret was not initialised with 0.

Workaround
not applicable

Test Procedure
Print to a Windows Printer when BSE_TMP directory is made read-ony.
The temporary printfile (tmpxxxxxx.bpf) should be created now in the system temp directory of the pc,
running BW.exe. And now make the BSE_TMP again accessable for read+write, and test again.
Now the temporary printfile should be created again in the BSE_TMP dir.

Affected Executables
bw.exe, bwprint.exe, etc

Scopus defectnumber(s)	Scopus casenumber(s)	Priority (e.g. 10)
100428			539782			20




--------------------------------------------------------------------------------
MaintCorelli: # 12098 (BDNT6131): BwPrint: do not use PutTextInBuffer when reordering is allowed

Date: Fri, 21 Sep 2001 16:09:14 +0200

Created on:  MaintCorelli
Type:        bugfix

Problem Description (Customer terms)
When reordering is set to 'allowed' in BwPrint (see project 6007),
the column order is corrupted as soon as Hebrew or Arabic text is printed.

Problem Description (Technical terms)
BwPrint in some cases uses spaces to separate the columns.
This is incorrect when reordering is active.

Test Procedure
ask Koen van den Dool

Affected Executables
bwprint.exe

Scopus defectnumber(s)	Scopus casenumber(s)	Priority (e.g. 10)
113636                  610587, 618197          20
112264                  595233, 596840          30



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

MaintCorelli: # 12003 (BDNT6007): BwPrint: make REORDER configurable

Date: Tue, 4 Sep 2001 09:16:39 +0200

Created on:  MaintCorelli
Type:        bugfix

Problem Description (Customer terms)
Arabic and Hebrew texts appear incorrect in BwPrint and on printer in some cases.

Problem Description (Technical terms)
Problems with standards.
Text in .bpf file should be in left-to-right display order, and BwPrint should do no reordering.
In some cases however, the bpf file contains the text in logical order,
and then BwPrint must use Windows to do some reordering.

Workaround
Use left-to-right display order in teh .bpf file.

Test Procedure
Test whether reordering option has correct value and is stored correctly in the registry.
Ask customer to do the real display and print tests.

Affected Executables
bwprint.exe

Scopus defectnumber(s)	Scopus casenumber(s)	Priority (e.g. 10)
113636                  610587, 618197          20
112264                  595233, 596840          30



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