List of changes for portingset: 6.1c.07.08 MaintBaanIVc: # 25893 (BDNT18449): Windows badmin: add support for retrieving password expiration warning info Date: Tue, 7 Jun 2005 18:36:36 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) To make the new 'change password' functionality work on BaanIVc on Windows, the Porting Set should tell 3GL whether the user's password will expire soon. Workaround n/a Test Procedure Run the command line mentioned above. Affected Executables badmin.exe MaintBaanIVc: # 25846 (BDUX18457): bic_bshell: Improve argument name in change.password() signature Date: Fri, 3 Jun 2005 13:05:50 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) See BDUX18456. Workaround See BDUX18456. Test Procedure none Affected Executables none MaintBaanIVc: # 25841 (BDNT18382): Msql7_maint: Pick up msql_serverhost from db_resource file. Date: Fri, 3 Jun 2005 12:35:54 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) Baan is installed on a Windows 2003 Cluster server, in combination with clustered SQL Server. After creating a new database user in session ttdba0115m000 (Maintain Database Users), or changing the current password, you select this user and press "Convert Users". The conversion fails, and the following error is reported: (ttdba01155) Error 1 occured while executing program. After pressing OK, the following error is reported: (ttdbadll02) Error from Database Maintain program: test -1 1|Connect error 0 from 'Microsoft SQL-DMO (ODBC SQLState: 08001)' as 'sa' to server '(local)'. [Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied. And the following error is logged in the Windows Event Log: Env BaanIV (r:\baan4c) Prog Msql7Adm.dll file R:\db\servers\MSQL\msqladm.cpp # 2287 Process 0x3c8 Thread 0x430 Lasterror 0 Errno 0 Message Microsoft SQL-DMO (ODBC SQLState: 08001) returned error 0: [Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied. [Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()). Test Procedure Have Baan installed on a Windows2003 / SQL Server 2000 Windows cluster server. Log in, and open session "Maintain Database Users" (ttdba0115m000). It should be no problem to create a new database (inclusive conversion), or change the password of an existing user. No errors should be reported. Affected Executables msql7_maint.exe Motive source DF:224831 MaintBaanIVc: # 25828 (BDUX18437): Removed escape characters in informix database scripts Date: Thu, 2 Jun 2005 09:51:03 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) The informix database installation scripts shows escape characters on Linux. Workaround n/a Test Procedure run inf_admin6.1 and inf_install6.1 scripts. Affected Executables inf_admin6.1 inf_install6.1 MaintBaanIVc: # 25786 (BDUX18402): Merge (old) bic line number improvements to MaintBaanIVc Date: Fri, 27 May 2005 15:00:59 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) In an incorrect assignment in a 3GL script, some errors do not provide the line number of the assignment. Workaround Don't make errors in assignments :-) Test Procedure Just one example: compile the following (erroneous) script: function extern main() { long l l = "bla" } This should result in the following output: ptest0( 5): Error: Illegal type combination: 'long = string' ptest0( 5): Error: Dimensions in array assignment differs: 0:1 2 ERRORS REPORTED. instead of this WRONG output: ptest0: Error: Illegal type combination: 'long = string' ptest0: Error: Dimensions in array assignment differs: 0:1 2 ERRORS REPORTED. Affected Executables bic MaintBaanIVc: # 25753 (BDUX18287): rptcvt core dump when row data does not match with layout Date: Wed, 25 May 2005 13:06:28 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) The real problem is that the layout definition doesn't match with the actual row data for the same layout rptcvt core dumps when this happens Test Procedure See Defect 155879 Affected Executables rptcvt6.1 Motive source DF:155879 MaintBaanIVc: # 25743 (BDNT18232): Installer issues on clustered W2003 SQL Server 2000 Date: Wed, 25 May 2005 10:43:52 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) When installing Baan against a clustered SQL Server 2000 on Windows 2003, the installer does not work correctly. Installer does not "recognize" the SQL Server instance on this configuration and some other problems. Test Procedure Install BaanIVc on the following configuration: Windows 2003 cluster SQL Server 2000, installed in cluster mode. (So SQL Server 2000 is already cluster-aware, and supporting fail-over, before you start installing Baan. Note that in the past you needed to make SQL Server cluster- aware after you installed Baan!). Affected Executables msqladm.dll setup.ins Motive source DF:221771 MaintBaanIVc: # 25738 (BDUX18327): Increase of pty usage after BDUX17260 Date: Wed, 25 May 2005 10:33:11 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) After installing portingset 6.1c.07.07 the following error was reported: Errno 24 (The process file table is full) bdb_errno 0 Failed to open pty pair. After increasing the number of pty's from 256 to 512 the problem was solved. It looks like the pty usage increased after installing this portingset. Workaround Increase the number of available pty's on system level. E.g. double the number of available pty's. Test Procedure Before logging into Baan, set the following in to the Command field of Bw Configuration: -- -dbgpty -logfile ptytrace -keeplog Log in Baan, and from the menubar select File->Run Program. Fill in: ksh, and check "Run External Program". Press OK. Now a terminal emulator is opened. Type exit and leave the terminal emulator again, and log out Baan. Afterwards check the ptytrace file, it should contain: pty: opened master /dev/ptc fd 9 pty: opened slave /dev/pts/2 fd 10 PTY STRUCTURE PTY: proc = ottstpvtemul_r PTY: in = 12 PTY: out = 9 PTY: mfd = 9 PTY: pfd = 12 PTY: rpid = 0 PTY: spid = 32416 PTY: flags PTY: no input for process ottstpvtemul_r pty: opend slave /dev/pts/2 fd 13 So 1 master pty should be opened. In a wrong situation you will see 10 times "pty: opened master /dev/ptc fd ..". Affected Executables bshell Motive source DF:156103 MaintBaanIVc: # 25621 (BDUX17389): Diagnostic functionality in api6.x Date: Tue, 17 May 2005 08:51:12 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) Customers had no independent means of knowing if their environment was setup properly for use with Taxware or Vertex. They had to set everything up and then try to use it through Baan. Workaround Customer had to start Baan with various debuggin environment variabls set in order to get any kind of diagnostic information to help them fix any kind of setup issues. Test Procedure After building a new api6.x (Unix only) or installing the new portingset (Windows) the api executable can be run from a command prompt with -dt (Taxware) or -dv (Vertex). This will dump a number of lines of information to the screen and if anything is wrong with the environment variables or the tax installation there should be a message included to help pinpoint what the issue is. Affected Executables api6.x/api.exe Motive source DF:224071 MaintBaanIVc: # 25514 (BDUX18137): Enhance error messages Date: Tue, 3 May 2005 16:14:48 +0200 (CEST) Created on: DevDvorak Type: bugfix Problem Description (Customer terms) String demotion when concating strings into a tmp string: string desc80(80) mb string shortcut(10) long length length = len(desc80 & shortcut) results in the length of bytes of the result string while number of characters is expected. the temporary string created by the concat disregards the fact that one of the strings is a multibyte string Workaround in the example add: string temp.mb(90) mb change: temp.mb = desc80 & shortcut length = len(temp.mb) Affected Executables bshell6.2 MaintBaanIVc: # 25504 (BDUX18049): Long passwords on HP UX trusted security. Date: Tue, 3 May 2005 11:36:10 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) Using HP-UX OS in "Trusted Security" mode, and using BaanLogin protocol to log in Baan: When using passwords bigger than 8 characters, you cannot log in Baan. An Authorization Failure error is reported. Workaround Do not use passwords longer then 8 characters. Test Procedure You need to have a HP-UX system, running in "Trusted Security" mode. When having such system, running Baan, set the user-password to a password longer then 8 characters. (not longer then 25 characters). You should be able to log in Baan using the Baan Login protocol when using password longer then 8 characters. Affected Executables blogind6.x Motive source DF:155293 MaintBaanIVc: # 25498 (BDUX18136): Unexpected locks on AIX platforms. Date: Mon, 2 May 2005 16:43:20 +0200 (CEST) Created on: MaintMahler Type: bugfix Problem Description (Customer terms) Unexpected database locks are occured on AIX platforms. This problem was found during a Gemini installation. Workaround n/a Test Procedure Test was done with a complete Gemini installation on AIX. No easy test is available. Affected Executables inf_srv6.x MaintBaanIVc: # 25434 (BDNT18074): BDNT18008 (Winstation test based on 7.1d.05) Date: Tue, 26 Apr 2005 13:02:04 +0200 (CEST) Created on: MaintBaanIVc Type: porting specific change Problem Description (Customer terms) See BDNT18008 Workaround See BDNT18008 Test Procedure See BDNT18008 Affected Executables See BDNT18008 Motive source DF:1019020 MaintBaanIVc: # 25419 (BDUX17991): Oracle driver: function definition sync between BaanIV and BaanERP Date: Mon, 25 Apr 2005 17:07:30 +0200 (CEST) Created on: MaintBaanIVc Type: porting specific change Problem Description (Customer terms) Performance gap between ora7_srv and ora8_srv. Test Procedure Regression tests Affected Executables ora8_srv ora8_maint MaintBaanIVc: # 25405 (BDNT17986): Api messages invalid, error code 1 Date: Mon, 25 Apr 2005 10:59:03 +0200 (CEST) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) API message was invalid. Error code 0. API request failed. Message was not sent. Error code 1. Workaround N/A Affected Executables api.exe MaintBaanIVc: # 25387 (BDNT17475): Log errormessage when bshell cannot register at licence server. Date: Fri, 22 Apr 2005 10:39:02 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) When logging into Baan nothing happens, and the following error appears: 1 : Error: Time out. We do not understand what the problem is. What is timing out? Workaround No Test Procedure Could only be tested at customer system, where another application was listening on port 6003. (port 6003 is the port being used by the Baan Licence server) Affected Executables bshell Motive source DF:155647 MaintBaanIVc: # 25375 (BDNT18018): Add new axbarcode.lic file Date: Wed, 20 Apr 2005 16:02:33 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) BwPrint: The barcode functionality is not enabled. (Menu options regarding Barcode's are grayed out) Workaround Create the following registry setting: HKLM\SOFTWARE\dLSoft\abc key (type REG_SZ) "Current" value data: "version 30" Test Procedure Have the new bwprint, axbarcode.ocx and axbarcode.lic installed. Start BwPrint. From the Help select Barcode Test. The Barcode Test should show the barcode images. Affected Executables Bwprint Motive source DF:224085 MaintBaanIVc: # 25368 (BDNT17416): Determination of mac address via Netbios not reliable. Date: Wed, 20 Apr 2005 13:45:34 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) BaanIVc installed and validated successfully. But after restart of the Windows2000 server, the Baan Licensing service does not start anymore. The following error is logged in the Windows Event Log: Can't run - Please brand your software. Also after applying use_enhanced_hostid:1 (refer to solution 131733) and re-validating Baan, the same problem comes back after a restart of the system. Workaround No Test Procedure It is not possible to define a test procedure for this problem. The problem seems to be related to the number of times networkadapters/protocols/services were installed/uninstalled at a Windows platform. Affected Executables licd.exe, licmon.exe, brand.exe, hostid.exe Motive source DF:155502 MaintBaanIVc: # 25366 (BDUX18015): QP: Each sql_exec of query with _compnr = :1 scans through tabledef Date: Wed, 20 Apr 2005 12:22:01 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) A query that has a _compnr = :1 clause, gives bad performance if the tabledef file has a lot of entries and the query is executed multiple times. Affected Executables bshell qptool Motive source DF:153936 MaintBaanIVc: # 25344 (BDUX17992): Oracle driver: shared Oracle library based Date: Mon, 18 Apr 2005 16:23:44 +0200 (CEST) Created on: MaintBaanIVc Type: porting specific change Problem Description (Customer terms) All Oracle drivers are now Shared library based Test Procedure nightly build regression tests Affected Executables ora8_srv ora8_maint MaintBaanIVc: # 25316 (BDUX17937): expression range problem with float domains Date: Thu, 14 Apr 2005 13:21:26 +0200 (CEST) Created on: DevDvorak Type: bugfix Problem Description (Customer terms) Field "Planning Factor" wrong calculation with decimals, Error 205 Test Procedure function main() { double aa double bb double cc long e.id long aa.e long bb.e long cc.e e.id = expr.compile("$$ in [0.01,0.99]") aa = 0.01 bb = 0.0099999997764825821 cc = 0.99 | | internally ranges are compared with a tolerance of 0.0000009 | aa.e = l.expr(e.id, aa) | returns 1 bb.e = l.expr(e.id, bb) | used to return 0 returns 1 now cc.e = l.expr(e.id, cc) | returns 1 aa = 0.009 aa.e = l.expr(e.id, aa) | returns 0 aa = 0.0099 aa.e = l.expr(e.id, aa) | returns 0 aa = 0.00999 aa.e = l.expr(e.id, aa) | returns 0 aa = 0.009999 aa.e = l.expr(e.id, aa) | returns 0 expr.free(e.id) } Affected Executables bshell6.2, db drivers Motive source DF153060 MaintBaanIVc: # 25313 (BDUX17920): NQP: Improve performance of inner joins Date: Wed, 13 Apr 2005 16:46:13 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) A SQL statement containing an inner join performs badly if it is executed with the OpenWorld ODBC connector. Test Procedure Execute a query like the following with DBSLOG=400, for example using bsql with the -p16 option (prepare in ANSI mode): select * from dbtst190 a inner join dbtst120 b on a.empno = b.empno and a.company_nr = b.company_nr where a.company_nr in (0,1) and a.empno in (10,100000) Observe in the dbs.log file that both tables (and the join) are handled in a single query to the RDBMS. Affected Executables jbdb library all database driver MaintBaanIVc: # 25284 (BDUX17917): add override_java_sigusr2 resource Date: Tue, 12 Apr 2005 15:15:18 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) On Linux now and then the bshell hangs or a connection is broken after tmboaserver is started. Test Procedure start tmboaserver it succeeded already most of the times without this fix Affected Executables bshell MaintBaanIVc: # 25262 (BDNT17890): Sort: extra modification BDNT17786 Date: Mon, 11 Apr 2005 12:26:15 +0200 (CEST) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) Refer to project BDNT17786 Workaround Not applicable. Test Procedure Refer to BDNT17786 Affected Executables sort.exe Motive source DF:224137 MaintBaanIVc: # 25243 (BDNT17839): Cannot login after install portingset 7.1d.08 due to uppercase characters in username Date: Fri, 8 Apr 2005 14:13:46 +0200 (CEST) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) Cannot login after install portingset 7.1d.08 due to uppercase characters in the username on Windows. In Windows a user can have a username with uppercase characters, in Baan the username is always lowercase. A comparison fails. Because of that the user cannot be found in the Baan database users file. Workaround Change the username on Windows to lowercase. Test Procedure Create a user in Windows (or rename an existing one) with a username containing uppercase characters. Start Baan with that user. Affected Executables Database drivers Motive source DF:155137 MaintBaanIVc: # 25226 (BDNT17856): BwPrint: Update of barcode control Date: Fri, 8 Apr 2005 10:37:41 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) Check the barcode output for Code39 and Extended Code39 with a barcode reader. The "-" in the extended Code39 is being represented as a "/M" character. The "-" in the extended Code39 should be represented as a "-" character. Workaround No workaround Test Procedure Tested by the customer, by scanning the Extended Code39 with "-" character. Affected Executables bwprint.exe Motive source DF:224085 MaintBaanIVc: # 25198 (BDNT17786): Sort: incorrect name of sort files Date: Wed, 6 Apr 2005 11:33:42 +0200 (CEST) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) About 2 weeks ago started receiving the Sort Error 6 "No more files can be created in this moment" when running various reports in Baan. The tf module is of the most concern, because when printed out checks and received the error mentioned above, the checks came out in a Supplier # order, rather than Supplier Name alphabetical order and it took a lot longer to match them up to invoices, sorted in alphabetical order. Running on Windows 2000 (SP4) Workaround There is no really good workaround. Rebooting the server once a day might prevent the problem to happen. Test Procedure Problem is specific for Windows os, because Windows does not allow characters like "?" and ">" in the file name. So you need to test this on a Windows os. Further, you can only test this fix when you are sure that the pid of sort.exe consist of 6 digits or more. E.g. 150184. This happens only when you'r windows system is running for a longer time, and pid's becomes larger. If you have a pid of 6 digits (or more), you can run for example session ttadv4450m000 (Print Messages) to test. At "Sort by" select for example "Pack/VRC/Lang/Message" and at Package (From/To) select for example tc/tf. Now when running this session sort.exe will be called in the background and used to do the sorting. Sort should not generate error 6 "No more files can be created in this moment". Affected Executables sort.exe Motive source DF:224137 MaintBaanIVc: # 25194 (BDNT17790): Job Daemon cannot be started Date: Wed, 6 Apr 2005 11:32:50 +0200 (CEST) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) Baan Job Deamon service couldn't be started anymore after 7.1d.08 installation Workaround Use the jobd.exe from the previous portingset (7.1d.07) Test Procedure Start the job daemon on windows, check the logging event viewer. Affected Executables jobd.exe Motive source DF:154634 MaintBaanIVc: # 25095 (BDUX17729): Overflow format error when printing to Windows printer on Linux Date: Wed, 30 Mar 2005 11:45:20 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) When printing any report using a "Windows Printer" device you always got error "Overflow format='9999' 'value='xxxxxxxxxx' where 'xxxxxxxxxx' is a random number. This is only happening om Linux platforms. Workaround N/A Test Procedure On a Linux environment print any report to a windowsprinter. Use 'Print Preview'. A BW message will popup with an overflow error message. This fix will prevent the error. Affected Executables bshell6.x Motive source DF:154343 MaintBaanIVc: # 25090 (BDUX17698): Shmmanager do not allow hash signs in shm_param file Date: Wed, 30 Mar 2005 08:32:12 +0200 (CEST) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) Shmmanager do not start on Linux Motive source TCS:800-146596 MaintBaanIVc: # 25081 (BDUX17716): Page breack does not trigger footer and header layout. Date: Tue, 29 Mar 2005 15:07:52 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) After page break layouts are missing. Workaround No workaround. Test Procedure Tested on the Charger: Package combination O_stndc4, company 650 Start session tdsls4401m000, select Specific Order, select Sales Order 418. Set Order Line Type to "All Lines", Print to device D66 for example. Eech page should contain an header. Affected Executables repgen6.1 Motive source DF:154276 MaintBaanIVc: # 25040 (BDNT17648): Cannot login to Baan when PATH is too long Date: Wed, 23 Mar 2005 15:07:41 +0100 (CET) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) The system environment variable PATH became too long for Baan to be handled. Shortening the PATH variable solved the problem. This defect is logged to prevent this error from occurring. In case the PATH variable is too long to be handled, it should not cause the baan system to function. In stead the PATH should also be handled in case it is more than 1024 characters Workaround Take care that the value of PATH is smaller than 512KB, and the expanded value is smaller than 1024KB. (e.g. when PATH=%BSE%\bin;%PATH%, %BSE% and %PATH% will be expanded). Test Procedure Into the windows registry, HKEY_LOCAL_MACHINE\SOFTWARE\Baan\\Environment, add the following value: Name: PATH Value: insert a value which contains %BSE% and %PATH% for example. (like: %BSE%\bin;%PATH%) Take care that the system PATH variable is larger than 1024 characters. The following should be possible now: - logging in Baan - Start Baan NT Manager, right-click the environment, and select "Environment variables...". The window popping up should show you also the PATH variable correctly. - Start Baan MMC NT Manager, right-click the environment, and select "Properties" Select "Environment" tab now. The PATH variable should be displayed correctly now. Affected Executables rexecd.exe bentman.exe baanman.dll Motive source DF:154558 MaintBaanIVc: # 25000 (BDNT17124): BW: Circles filled incorrectly when running via Terminal Server client Date: Fri, 18 Mar 2005 12:03:47 +0100 (CET) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) Filled circles are drawn larger than they should be on Windows 2003 Terminal Server. For example: Start "Display Business Process" (tgbrg5501m000) session the "state" symbols are drawn incorrectly. The filling of the circle is twice the diameter of the black outline, the diameter of both should be identical. Workaround No workaround. Test Procedure When testing, run BW via a Terminal Server client, because the problem specially occurs when running BW via a Terminal Server client. 1) Compile and run the following testprogram: long Mwin.id, Gwin.id function main() { show.mwindow() add.pie() update.object(Gwin.id) update.object(Mwin.id) message("Klaar") } function show.mwindow() { Mwin.id = create.object( DsCmwindow, 0, DsNtitle, "Taarten bakken", DsNprocessgroup, get.pgrp(pid), DsNminWidth, 550, DsNminHeight, 250 ) Gwin.id = create.object(DsCgwindow, Mwin.id, DsNwidth, 550, DsNheight, 250, DsNpointerCursor, DSCHAND ) update.object(Mwin.id) update.object(Gwin.id) } function add.pie() { long pie.id | line 2694 ptgbrgprocobj0 pie.id = create.sub.object(Gwin.id, DsCgpPie, DsNangle, 0, DsNgcBackground, 14474460, DsNgcFillColor, 9414824, DsNgcFillStyle, GCFILLSOLID, DsNgcForeground, 0, DsNgcLineStyle, GCLINESOLID, DsNgcLineWidth, 1, DsNheight, 34, DsNrotation, 360, DsNwidth, 34, DsNx, 50, DsNy, 50 ) update.object(Mwin.id) update.object(Gwin.id) pie.id = create.sub.object(Gwin.id, DsCgpPie, DsNangle, 0, DsNgcBackground, 14474460, DsNgcFillColor, 9414824, DsNgcFillStyle, GCFILLSOLID, DsNgcForeground, 0, DsNgcLineStyle, GCLINESOLID, DsNgcLineWidth, 2, DsNheight, 34, DsNrotation, 360, DsNwidth, 34, DsNx, 200, DsNy, 50 ) update.object(Mwin.id) update.object(Gwin.id) pie.id = create.sub.object(Gwin.id, DsCgpPie, DsNangle, 0, DsNgcBackground, 14474460, DsNgcFillColor, 9414824, DsNgcFillStyle, GCFILLSOLID, DsNgcForeground, 0, DsNgcLineStyle, GCLINESOLID, DsNgcLineWidth, 0, DsNheight, 100, DsNrotation, 340, DsNwidth, 100, DsNx, 350, DsNy, 50 ) update.object(Mwin.id) update.object(Gwin.id) } Result: all circles (2) and the pie should drawned correctly. 2) Run tgbrg5100m000 (Maintain Business Processes in Repository). Select a Business Process. Press Editor (tgbrg5101m000) Now the "state" symbols should be drawned correctly. Affected Executables bw.exe Motive source DF:154019 MaintBaanIVc: # 24987 (BDUX17579): NQP: select array column indexed by non-selected column gives crash Date: Thu, 17 Mar 2005 17:23:01 +0100 (CET) Created on: MaintMahler Type: bugfix Problem Description (Customer terms) The database driver crashes if the select clause of SQL statement contains an array column indexed by another column that is not by itself in the select clause. The following query is an example: select dblarr(longarr[1]) from dbtst190 where empno = 10 Test Procedure Execute a query similar to the following query: select dblarr(longarr[1]) from dbtst190 where empno = 10 Affected Executables All database drivers MaintBaanIVc: # 24970 (BDUX17570): Extend xml tracing to catch invalid access to xml nodes (II) Date: Thu, 17 Mar 2005 11:35:20 +0100 (CET) Created on: DevDvorak Type: bugfix Problem Description (Customer terms) Not all access to invalid/freed xmlNodes where traced. Test Procedure See BDUX17398 Affected Executables bshell6.2 Motive source TCS:800-145787 Total number of changIDs displayed: 35