Bugfixes BW version 7.1c.03.144 =============================== MaintCorelli: # 12994 (BDNT6855): Error in Application start termination reason value Date: Thu, 17 Jan 2002 14:07:29 +0100 Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) After closing the Dynamic Form Editor, the session "Sessions" comes up with the error message: "Cannot start Dynamic Form Editor". Problem Description (Technical terms) This error is introduced with bugf_BDNT6166. The existing reason codes for the terminate application events where changed due to the addition of a new reason code. Workaround Just ignore this message. Test Procedure See problem description Affected Executables bw.exe Scopus defectnumber(s) Scopus casenumber(s) Priority (e.g. 10) 203878 916882 20 (this was the original remark). -------------------------------------------------------------------------------- MaintCorelli: # 12904 (BDNT6788): Make sure available config object always registered Date: Thu, 10 Jan 2002 09:06:12 +0100 Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) The Corelli bwc.dll is registered on a client one time and never updated. This causes some maintenance issues as the customer currently has four different Central Deployment environments running on two code servers. These different shares are used to test and roll BW to production, so there may be different versions of (Corelli) BW in place on each share. The current bwc.dll registration scheme will not support this type of configuration. Since the bwc.dll registration information essentially becomes "hardcoded" on a client, it binds the client to one version/path for bwc.dll loading until the registry is altered manually. In addition, if a Central Deployment share goes offline, all clients bound to that share by their registration of bwc.dll will fail until their registries are manually altered. The bwc.dll needs to be changed to reregister itself everytime that BW is loaded. Problem Description (Technical terms) See problem description Workaround Clear registry by hand. Test Procedure See problem description. Affected Executables bw.exe Scopus defectnumber(s) Scopus casenumber(s) Priority (e.g. 10) 120917 930777 20 -------------------------------------------------------------------------------- MaintCorelli: # 12706 (BDNT6694): BW: Looping when you do not want to reconnect Date: Fri, 21 Dec 2001 12:14:51 +0100 Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) BW.exe is looped when it is connected to Baan. The user that a problem happens is a normal user. This user has the use time of Baan restricted with "User data Template". The following message is indicated when BW.exe is started in the time when it isn't authorized. 1.bw Cannot setup a connection with the Bshell 2.bw Connection with server lost reconnect ? 3.BW Messages 1:No permission to run at this time "Yes(Y)" is chosen for the question of "Connection with server lost reconnect ?". Again, "NO permission to ru at this time" is indicated in BW Messages and "Connection with server lost Reconnect?" is indicated in BW. "Yes(Y)" is chosen in succession for "Connection". It is repeated about four times. "No(N)" is chosen for "Connection with server lost. Reconnect?". BW.EXE is looped here. Problem Description (Technical terms) After setting up connection with bshell fails with IDS_BSHELL_ERROR, a failure message is popped up. But because in the meanwhile the message from the BwCommErrorHandler comes, not the failure message is popped up, but the Reconnect message. This causes undesired behaviour. Workaround Immediately press OK on the first message window, before the Reconnect message comes. Test Procedure Refer to problem text (customer text). Now only a message "Cannot setup a connection with the Bshell" pops up. (And the BW Message windows showing you the error "No permission to run at this time"). After pressing OK, the following message pops up: "An error occured while executing BW. See the message window for a detailed error message.". After pressing again OK no new message window pops up. Close the BW Message window. Affected Executables BW.exe Scopus defectnumber(s) Scopus casenumber(s) Priority (e.g. 10) 119321 644126 30 -------------------------------------------------------------------------------- MaintCorelli: # 12703 (BDNT6166): BW: Problems starting application via a shortcut (lnk) Date: Fri, 21 Dec 2001 12:13:02 +0100 Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) In order to standardize the path, a shortcut is created to wordpad which is going to be to placed in c:\ on every client, and a new device is created, to access it, as follows: Device : DOWNLOAD_TEST Description : *** Testing *** DO NOT USE *** Device Type : Rewrite file Locale : ISO-8859-1 Western Europe - 8 bit --Printer ----------------------------------------- Driver : Device Queue : Paper Type : Left Margin : Form Feed : --File ------------------------------------------ Driver : Shell Command : 4GL Program : ttstpconv Argument : monarch c:\wordpad.lnk Path : c:\baanfile Change allowed : No Page Length : 66 At first, it seems to work fine, because the output file comes up in wordpad as expected, but a BW window also opens up with the following message: Microsoft Visual C++ Runtime Library Runtime Error! Program C:\PROGRAM FILES\BAAN\BIN\BW.EXE R6025 - pure virtual function call Also sometimes the following message is given: BW application error An error occured while running BW. For more information, refer to logfile BW.log or the NT event viewer. Problem Description (Technical terms) When starting the shortcut via the ShellExecuteEx command, the return value indicates the process is started successfully. However, the process handle (sei.hProcess) is not filled. Because the process handle is not filled this leads to undesired behaviour of the AppletSynchronizer. Made modifications to handle the empty process handle correctly. Workaround Do not use a shortcut but specify the full path or take care the application can be found via the PATH variable. Test Procedure Create a Baan device as described in the problem text (customer terms). Create a shortcut which opens wordpad: c:\wordpad.lnk Print from a print session to this device. Now wordpad should correctly start and open the file c:\baanfile. No error (as described in the problem text) should appear. Repeat this about 20 times to be sure it works correctly, because timing was an issue. Affected Executables bw.exe Scopus defectnumber(s) Scopus casenumber(s) Priority (e.g. 10) 203878 916882 20 -------------------------------------------------------------------------------- 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: # 12509 (BDNT6463): Allow configuration change from BW Date: Fri, 7 Dec 2001 14:43:26 +0100 Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) Customer is needing to regain functionality of the Run, Save and Save As buttons that have been removed in BW versions 7.1c.137 and 143. Aside from another defect that is an enhancement request to get those buttons back this defect is geared toward adding the ability after saying OK in the BW Config window to prompt the user to whether you want to save or not. This is a problem in Central Deployment because users do not have access to BECS. Also the following problems are observed with BECS: 1) The keystrokes: CNTRL-C, CNTRL-V do not work (copy/paste). 2) Single click the name of a bwc-file in BECS does not always activate the Rename functionality Problem Description (Technical terms) This problem is solved as follows. The following scenario is folowed: 1. A user can press configure from the BW password dialog. 2. Change some settings in the configuration screen. 3. Press OK: User will be asked whether to save the new settings or not. 4. User answers:NO. BW login dialog appears again using the modified (but not saved) configuration settings OR 5. User answers YES. 6. BW login dialo appears again using the modified and saved configuration settings. Workaround Use difference .bwc files. Test Procedure See problem description above. Affected Executables bw.exe becs.exe Scopus defectnumber(s) Scopus casenumber(s) Priority (e.g. 10) 205003 924707 30 -------------------------------------------------------------------------------- MaintCorelli: # 12332 (BDNT6386): Do not sent pageup and pagedown keys from listbox Date: Wed, 7 Nov 2001 12:18:37 +0100 Created on: Reger Type: bugfix Problem Description (Customer terms) When you press pagedown or pageup in a listbox an internal ASSERT is generated in the 4GL-Engine in any 4GL-Session with a drop-down listbox. Problem Description (Technical terms) PageUp and PageDown generate a listbox select event and should therefore not be reported as a keypress event to the Bshell. Workaround Don't use these keys to select items. Test Procedure See problem description. Affected Executables bw.exe -------------------------------------------------------------------------------- MaintCorelli: # 12328 (BDNT6383): Scroll grid cell in view does not always work Date: Wed, 7 Nov 2001 12:15:51 +0100 Created on: Reger Type: bugfix Problem Description (Customer terms) Start Project Hours (bptmm1111m000). Insert two records without intermediate save action. When focus is on last field of the first record, and giving TAB, the focus will be on the first field of the second record. However this is not visible. The horizontal scrollbar is not moved to the beginning. Problem Description (Technical terms) During the setValues the Grid is locked for updates (to improve performance). However the Grid code skips scrolling the cell into view when the grid is locked for updates. Workaround Scroll using the horizontal scrollbar. Test Procedure See problem description. Affected Executables bw.exe -------------------------------------------------------------------------------- MaintCorelli: # 12319 (BDNT6376): Dropdown listbox not resized when updated Date: Tue, 6 Nov 2001 14:53:51 +0100 Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) The Dropdown Combo Box from field Financial Transaction changed after selecting a different Transaction Origin. The length was shortened and the arrow disappeared. This problem occurs in the Find-window from session tfgld4532m000: Integration Transactions Log. Problem Description (Technical terms) When a change of the list items is done by the backend while the dropdown listbox is currently in drop-down state, the resize was inhibitted. The solution is to delay this resize. Workaround Use TAB key to move focus. Test Procedure See problem description. Affected Executables bw.exe -------------------------------------------------------------------------------- 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: # 12301 (BDNT6328): Enhance file and directory access check for Windows Date: Thu, 1 Nov 2001 15:48:27 +0100 Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) In case of Windows OS: BW does not fall back to system TEMP, in case BSE_TMP is not accessable with READ+WRITE permissions. Problem Description (Technical terms) When expanding BSE_TMP variable, by get_bse_tmp, also an access check is done on the path. Function access() is used to check the access. But this function does not work as expected on Windows OS. It does only work in case a file or directory has Read-Only attribute. But in case the NTFS permissions are set to Read-Only it is not detected by access(). Workaround Change permissions of BSE_TMP directory. 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. Affected Executables bw.exe and all other executables using get_bse_tmp. Scopus defectnumber(s) Scopus casenumber(s) Priority (e.g. 10) 100428 539782 20 --------------------------------------------------------------------------------