Generator Visual Basic 9.0 Release Notes UPGRADE # 3 Important • A new version of the following dlls is installed in this Upgrade: gxoffice2.dll must be updated in client workstations and PCs in case of using it. • To make the changes of this upgrade effective, once installed, the .VER , .ARI and .VBP files must be deleted and a forced application build all must be performed. Corrected Errors • SAC # 18461 - IsValid in Work Panel with several grids only works in one We have a Work Panel with two grids. We program the IsValid event for columns of both grids to return the description associated with the entered code. IsValid only works for one of the columns, not for all that were programmed. • SAC # 20456 - Corrections to dates in mysql Problems in dates handling were corrected: - Addition of days to dates - Dates that must be transferred as constants were transferred as string instead of using STR_TO_DATE. • SAC # 20712 - Val function not evaluated in MySQL server If in a procedure For Each a condition is added by using the Val function for evaluation in the server, the generated select is done as if the Where didn't exist. This happens with MySQL. • SAC # 20721 - Year function not evaluated in server in MySQL server 4.0 Year function not evaluated in server in MySQL server 4.0. • SAC # 21459 - SQL0417 with table update in iSeries It gives the error "SQL0417 – Invalid combination of parameter markers" when updating a field through an arithmetic operation. • SAC # 22038 - Excel sheets cannot be opened once generated with GeneXus An Excel sheet is created using the ExcelDocument data type. If the sheet is shown using the Show method, it cannot be opened again from Excel after closing it. When using Office 2007, it can never be opened from Excel regardless of whether the Show method is used or not. • SAC # 22203 - Argument not optional when adding parameter to Main object A main object with a parameter is generated and compiled with no problems. If a new parameter is added and generated, the "Argument not optional" error occurs when compiling it. • SAC # 22264 - Line validation problem in two-level TRN We have a two-level TRN and an error rule associated with one of the second level attributes that is also a foreign key. When the TRN is executed and a value is entered for the code (the foreign key) of the second level, the inferred data is not displayed and non-existent codes can be entered. • SAC # 22279 - VB code is repeated in Work Panel with more than one grid We have a Work Panel with more than one grid. When generating it in VB 9.0, the code generated for validating the grid is repeated 3 times. • SAC # 22320 - Error 438 when executing Work Panel with read only fields. The error "Runtime error: 438 Object doesn't support this property or method" occurs when executing a work panel with all its fields in read only mode. The problem appears when the Color in read only fields = Original property is used. • SAC # 22407 - Problems with text functions The DFROPEN, DFWOPEN and DFRGTXT functions changed their behavior in VB as from VB 9.0 U2. • SAC # 22408 - dfwpnum() and dfrgnum() use different decimal separators The text functions dfwpnum() and dfrgnum() are using different decimal separators. The dfwpnum() function uses a point as decimal separator, but the dfrgnum() function uses a comma. • SAC # 22411 - Problem with prompt image in TRN when there is noaccept We have a TRN with a foreign key, and a conditional noaccept is programmed on that foreign key to enable or disable the foreign key depending on a condition. The problem is that the foreign key prompt is always disabled, unlike the attribute that is enabled or disabled depending on the condition. The problem appears when the Color in read only fields = Original property is used. • SAC # 22481 - NULL is not saved when the For Each is optimized We have a For Each that executes an update in an optimized way. The programmed update was Att = nullvalue(Att) and the Generate Null for Nullvalue = True property has been set. In this case, an empty is saved instead of a NULL. (If we have referential integrity in the server and it is a foreign key, this operation throws a referential integrity error). • SAC # 22720 - Grid records are not viewed correctly We have a Work Panel with a grid that has a base table where the records of a table are displayed. In the fixed area of the Work Panel we have a combo where a piece of data can be selected. The data related to it is displayed in the grid. The problem appears when we access the Work Panel more than once and select values in the combo. The second time we access the combo and select a value, the records are not displayed correctly. • SAC # 22821 - Foreign Key description in update is not inferred We have a one-level TRN that has a foreign key as last editable field. We access it in insert mode and records are added correctly. However, if we access it in update mode, when changing the foreign key value the inferred attribute value is not updated. The inferred value is updated only when clicking Confirm. • SAC # 23039 - FromXml of SDT doesn't load the second level We have a two-level SDT; a ToXml is performed and then a FromXml. The SDT data is not loaded at runtime. • SAC # 23142 - Referential integrity error is triggered prematurely We have an application where we set the Color in read only fields = Original property and enabled prompt buttons to be displayed. If in a TRN we use a Setfocus to place the focus on a field, a referential integrity error associated with a foreign key is thrown prematurely. • SAC # 23208 - Ref. integrity error is not triggered when using subtypes We have a TRN with subtypes defined on attributes of another TRN. In addition, rules have procedures that perform certain controls over those subtype attributes. The problem is that when executing the TRN, the referential integrity controls are not triggered for these subtype attributes. • SAC # 23215 - Problem when executing Stored Procedures in SQL Server It has been found that sometimes when executing a stored procedure from a C/S application against SQL Server 2000 with ODBC access (VB for example), the stored procedure doesn't return data correctly to the application. • SAC # 23287 - "Error sending data" when invoking Web Service from VB app. We invoke a Web Service generated manually in Java (not with GeneXus) and the "Error sending data" error occurs when invoking it. • SAC # 23307 - "Maximum Workfile lines" model property appears twice The model property "Maximum Workfile lines" appears under "User Interface" group and under "Temporary files" group. • SAC # 23314 - Problem reading text file in VB In some cases, problems occur when reading text files from VB, especially when they contain text with special symbols or accented characters. UPGRADE # 2 Important • To make the changes of this upgrade effective, once installed, the .VER , .ARI and .VBP files must be deleted and a forced application build all must be performed. New Features • SAC # 21695 - New DBMS property: "Lock retry count" It indicates the attempts to make when a sentence fails because it is trying to lock a record which is already locked. Corrected Errors • SAC # 12019 - VarChar are not shown in subfile on entering in UPD and DSP VarChar are not shown in subfile on entering in UPD and DSP. • SAC # 14317 - Error on transferring more than one SDT item as parameter A procedure is called from a work panel transferring two SDT items as parameter. On returning to the work panel, the values of the items transferred as parameter remain wrong. • SAC # 16849 - Error with conditional filter on datetime in AS with date There is a conditional filter on a datetime-type attribute, in a model against Db2 For Iseries. On executing, an error of the following type occurs: [SQL0180] Date, time or time indication value syntax is not valid • SAC # 17120 - Error when calling dfwptxt many times When a procedure that handles text functions is called many times, an application error is thrown. • SAC # 17227 - Problem with text functions on processing file There is a text file that is processed using functions dfrgnum, dfrgtxt, dfrgdate, etc. The problem is that error code -5: Wrong format is returned for some of the file lines. • SAC # 17660 - Problem on processing text file with several lines There is a procedure that has a loop to process a text file with several lines On executing the procedure, although the lines are processed there are error messages that should not appear. • SAC # 18026 - Problem with dfwptxt The dfwptxt function receives as optional parameter the length of the text to be printed in the file, the length you want to give to the field. This length is not taken into account. • SAC # 21198 - Focus remains in read only field in work panel There is a work panel with a read only field and other editable fields. If you setup the Color in read-only fields = Original model property, on executing the work panel the focus remains on the read only field. • SAC # 21267 - Refcall is not triggered in TRN grid There is a 2-level transaction or a 1-level transaction and the attributes are located in a grid in the form. Besides, there is a refcall rule to obtain the value of one of the attributes. In this case, the refcall rule is not triggered. It works properly in the TRN flat part or when working with the default form in 1-level transactions.