List of changes for BW version B40c.073 (portingset: 6.1c.07.02)
MaintBaanIVc: # 20500 (BDNT13625): Updated license text of installer
Date: Thu, 20 Nov 2003 10:37:35 +0100
Created on: MaintBaanIVc
Type: porting specific change
Problem Description (Customer terms)
Updated license text of portingset/bw installer
Workaround
NA
Affected Executables
setup.exe
MaintBaanIVc: # 20369 (BDNT13449): BW4: announceErase to avoid flashing menu browser
Date: Tue, 4 Nov 2003 09:38:19 +0100
Created on: MaintBaanIVc
Type: bugfix
Problem Description (Customer terms)
menu browser flashes too much
Test Procedure
See scopus defect.
Affected Executables
bw.exe
Motive source
DF:138604
MaintBaanIVc: # 20242 (BDNT13280): Generate logmessage if not allowed to re-use password info from bwc file
Date: Fri, 10 Oct 2003 17:00:55 +0200
Created on: MaintBaanIVc
Type: bugfix
Problem Description (Customer terms)
The password information is stored in the bwc file, in case people choose to save the password.
This password information is encrypted together with the username of the one who stored the password.
In case somebody runs this bwc file, it is checked if the current user is the same as the user who saved the password.
If this is not the case BW will ask for the password. (And not automatically re-use the saved password).
When running BW in the background (jobs), you do not see this password dialog. Therefore it looks like BW hangs, and it is
not clear what the problem is. Therefore it is desired to log something.
Workaround
take care correct person saved password
Test Procedure
1. Start the BW Configuration as follows:
e.g.:
C:\baan\bwbaan4c\bin\bw.exe /giveaway=kees /config C:\baan\bwbaan4c\lib\user\kappa_IVc.bwc
2. Type in the password, and select to save it
3. Make this bwc file the default bwc file within BECS
4. Doubleclick BW
Now the following message to logged:
Env Bse (c:\baan\bwbaan4c)
Prog BWCONFIG file \ui\bw\config\bwconfig.cpp # 285
Keyword BwConfig
Username baan type S language 2
Process 0x780
Lasterror 0
Errno 0
bdberrno 0
Message User 'kvddool' is not allowed to re-use password information from 'C:\baan\bwbaan4c\lib\user\kappa_IVc.bwc'
(Here user 'kvddool' is a different one for your test.)
Affected Executables
bw.exe / bwconfig.dll
Motive source
DF:216335
MaintBaanIVc: # 20077 (BDUX13100): Add Windows username to process set.
Date: Tue, 23 Sep 2003 16:29:36 +0200
Created on: MaintBaanIVc
Type: bugfix
Problem Description (Customer terms)
For the licensing of the BOI Builder, the username on the Windows server
is needed to get the username in sync with the username used for licensing
BOI Studio.
Test Procedure
Use the latest BW and Bshell, and compile and run a small 3GL script that
calls the new function long get.bw.username( ref string bw.username)
Affected Executables
bw
bshell6.1
MaintBaanIVc: # 20054 (BDNT13184): Portingset update: update also nlsinf directory
Date: Fri, 19 Sep 2003 14:40:50 +0200
Created on: MaintBaanIVc
Type: bugfix
Problem Description (Customer terms)
When updating the portingset the lib\nlsinf directory is not updated.
This directory should be updated as well. Because sometimes this information is updated.
Test Procedure
Before starting updating the portingset, empty directory lib\nlsinf.
Update the portingset by running the setup.
When setup is finished, the mentioned directory should be filled again.
Affected Executables
setup.ins
MaintBaanIVc: # 19878 (BDNT12773): BW4 crash when doing listbox select
Date: Wed, 3 Sep 2003 09:59:52 +0200
Created on: MaintBaanIVc
Type: bugfix
Problem Description (Customer terms)
An "Access Violation" message is being thrown kicking the user out of Baan when they change the YES/NO enum fields in tfcmg2123s000.
It seems to happen when the user is clicking "fast".
Workaround
Do not click very fast, one listbox selection after the other.
Test Procedure
STEPS TO BE FOLLOWED :
1.) Go to tfgld1101m000 via File, Run
2.) Click the "Group Insert" button and tab through all the fields on the top so that they default with values.
Then click the "Insert" button and put JB4 as the Transaction Type and then tab out.
Save and then highlight the record in the bottom that you just inserted and click "Transactions". If tfcmg2101s000 opens up, just click "Save and Exit".
3.) Once you do that you be at tfcmg2100s000. Click "Insert" and tab to the enum field labeled "Type of Transaction".
Select "Supplier Reconciliation" and then tab out (the rest of the fields should default). Click the "Maintain" button.
4.) tfcmg2102s000 will now be open. Select a record that has an "open" status and note the "Transaction Type" and "Doc Number" (example: ANP 19970369)
and then click "Special" and then "Select for Automatic Reconciliation".
5.) tfcmg2122s000 will now open. Insert the "Transaction Type" and "Document Number" from the previous session and press "Select".
6.) tfcmg2123s000 will now open (this is the session where the user is getting the error).
Notice the record that has YES in the enum field is the one you selected. You can change more to YES if you would like.
7.) If you change the YES/NO fields using the keyboard or mouse in a very fast way you should not get an Access Violation in BW.
Affected Executables
bw.exe
Motive source
DF:215487
MaintBaanIVc: # 19716 (BDNT12469): BW error messages on Windows XP
Date: Thu, 14 Aug 2003 11:02:07 +0200
Created on: MaintBaanIVc
Type: bugfix
Problem Description (Customer terms)
After setting up a job for session tdsls4223m000 and tfgld1407m000 to run overnight
and when the job runs it completes successfully. A message appears in the event viewer
under application messages "polygon not filled".
Workaround
n/a
Test Procedure
A windows XP client is needed to do this test.
- setup a job for a arbitrarily session
- activate the job for a specific time
- lock your XP client
- wait until the job was done
- unlock your client and look into eventlog for messages.
Affected Executables
bw.exe
Motive source
DF:138193
MaintBaanIVc: # 19182 (BDNT12341): fatal error objext xxx in process xxx not found
Date: Tue, 1 Jul 2003 15:59:41 +0200
Created on: MaintBaanIVc
Type: bugfix
Problem Description (Customer terms)
I have upgraded to windows client version 70 from version 69 today.
I noticed when going into ttaad4100 that after entering the password it asks for,
that I get a bw error message along the lines of
"fatal error object 4040 in process 1 not found".
The session then opens ok. I am logged in as a super user.
Workaround
n/a
Affected Executables
bw.exe
Motive source
DF:137291