Copyright 2005 by gINT Software. All rights reserved worldwide.
gINT Update README.TXT file
gINT 6 README.TXT
NOTES:
1. Some of the documentation below is in tabular form and requires that you view this document in a fixed font, e.g., Courier New. If in Windows Write, place the cursor at the beginning of the document, hold down the Ctrl and Shift keys and then press the End key. This will highlight the entire document. Or use the Edit menu, Select All. Then use the Character:Font menu item to select a font.
====================
6.1.036 10Apr2005
====================
1. Maintenance release
====================
6.1.035 13Mar2005
====================
1. Maintenance release:
A. The Texas Natural Resource Conservation Commission form under the Agency Reports page of our Web site did not work.
B. Most output conditions on the Border and Discrete Graphics tabs in text entities did not work.
C. Certain configurations of graphic table output did not work.
====================
6.1.034 06Feb2005
====================
1. Maintenance release:
A. Opening some version 4 files could cause the file to bloat to over a gigabyte in size and corrupt it. This problem was introduced in our automatic file translation to better handle Chinese Windows has been fixed.
B. Deleting rows in Input caused the program to save the changes immediately. This problem was introduced two releases back and is now fixed.
C. Running repair/compaction with the option marked to convert ACCESS '97 files to ACCESS 2000, caused the file to the unreadable by ACCESS. The files were translated properly but a version property was improperly set in the file. gINT had no problem with it. If you have such files that need to read by ACCESS 2000, merely re-compact in gINT.
====================
6.1.033 31Jan2005
====================
1. By default PDF export embeds fonts. This is mainly to accommodate non-roman based languages (Hebrew, Greek, etc.). This leads to a significantly larger PDF file. You can omit the embedding of fonts using the "Do not embed fonts into exported PDF documents" property of the File:System Properties dialog. You will find this under the "General" tab.
2. Input Table Groups:
A. Previously you could not assign a child table to a group different than its parent. This restriction has been removed.
B. If group name of a parent table is changed:
1. If a split screen child is the only dependent table, the new group is assigned without prompting.
2. If there are other dependent tables, you will be prompted if the change should be propagated to all dependent tables.
====================
6.1.032 29Nov2004
====================
1. Maintenance release.
2. In Utilities:Repair/Compact Databases, the default is to convert ACCESS '97 files (the gINT default) to ACCESS 2000. The main purpose for this is for better support for Chinese Windows environments (and any other double-byte languages). ACCESS 2000 handles the transition between double and single byte environments better than ACCESS '97. Note that gINT versions 5 and 6 can work equally well with ACCESS '97, 2000, or XP version files.
3. The AGS Checker (separate download at www.gintsoftware.com/support_updates_agschecker.html) has been updated to accommodate AGS version 3.1 files which will soon be officially released.
====================
6.1.031 08Nov2004
====================
1. Maintenance release.
====================
6.1.030 16Oct2004
====================
1. In the early '90s we made a design decision on how to store certain types of data. We became aware a few years ago that this storage structure was incompatible with operating system configurations that supported double-byte languages (Chinese, Japanese, etc.). Version 4 of the program (16-bit) was not affected by the problem. Until Windows XP, Versions 5 and 6 (32-bit) were also not affected by the problem as long as English (or another single-byte language) was used as the default language. Chinese, Japanese, etc. could still be supported. With Windows XP any support of double-byte languages in the operating system causes gINT to crash. Recently this has become a serious problem for some of our Chinese clients and we have fixed it.
We could have easily translated all of our data structures to be compatible with the double-byte environment. However, this would mean that version 5 could not read version 6 files, as they can now. Further, builds of version 6 prior to 6.1.030 could not read files opened by builds 6.1.030 or later. We instead decided to put in the code to maintain the data structures but still run under double-byte environments. This required two main areas of change:
1) The underlying program code needed to be changed in a number of areas. This is transparent to the end-user.
2) Some of our system table fields (not user-defined project or library table fields) had to have their field type changed. This item requires a translation. This will not affect any operation of the program. You may notice slightly more time to open some files the first time that the translation occurs. Further, older versions of the program (since version 5) can still work with the translated files. Forward and backward compatibility are still maintained.
If you have no intention of running under a double-byte environment, no special work is required.
If you wish to run gINT under a double-byte environment (e.g., Chinese) certain files must be translated first. To perform the translation you must be working under the single-byte environment (e.g., English). We have spent a great deal of time trying to get the translation to work under a double-byte environment but there appears to be no way to do so. Microsoft concurs. The program will not allow opening a non-converted file when under a double-byte environment since data corruption would occur. Our apologies for this inconvenience.
Files are automatically translated on opening. However, it could take a great deal of time to open all files one by one. A better way is to move to the Utilties:Repair/Compact Databases application and specify all the files at once. The files that must be converted are:
A. All library files (*.GLB) except the current library. The current library is automatically translated on startup.
B. All project files that have Site Maps in them. If you are not using site maps in projects (there will be a "Site Map" tab in Input if you are), there is no need to translate projects.
C. All data template files that have Site Map support.
D. All gINT Drawing files (*.GDW).
To select all the necessary files. You can select one group (click the browse button [...] right of the upper text box), save, relaunch and select another group. They will be added to the list.
SETUP.GSH also needs translation but this is converted automatically on start up.
If you have no drawing files, no site map support in your projects, and only one library, just bringing the program up once translates all required files. Once the files are translated you can switch to the double-byte environment and gINT will work properly. If at some later time you try to open a non-translated file while under a double-byte environment, you will receive a message saying that gINT cannot open it and that it must be translated under a single-byte environment. You would then need to switch back to English (or any other single-byte environment), open the file, and then switch back to the double-byte environment.
2. There are cases where there is a configuration problem which results in the inability of gINT to start. The " /debug" switch at the end of the Target specification of the gINT desktop short cut generates a file that helps tech support track quickly down the problem. This can be generated more easily by just holding the Shift key down on the keyboard when double clicking on the gINT desktop icon.
3. When previewing from Input, the program outputs all of the records in the current grid, except in the POINT table where only the PointID where the cursor is located is output. In the POINT table, to output more than one PointID, highlight the desired records. In other tables, to output just one record, highlight it.
====================
6.1.029 05Sep2004
====================
1. Maintenance release.
2. In Input, the File:AGS Files:Edit AGS File in Excel was very slow with files more than a few 100KB in size. We have sped up the process significantly.
3. The PDF driver has been updated and can be downloaded from the same Web page as the gINT 6 update. This update puts in better support for multiple languages.
====================
6.1.028 15Aug2004
====================
1. Maintenance release.
====================
6.1.027 12Jul2004
====================
1. Maintenance release.
2. The Check for gINT Update stopped working when we posting our new Web site (www.gintsoftware.com). References to Web pages in the code have now been fixed.
====================
6.1.026 30Jun2004
====================
1. Maintenance release. Mainly to fix a specific problem with licensing.
====================
6.1.025 20Jun2004
====================
1. Maintenance release.
====================
6.1.024 13Jun2004
====================
1. Maintenance release.
====================
6.1.023 16May2004
====================
1. Maintenance release.
2. The "Do Not Display" check box field property has been moved in the Data Design:Project Database and :Library Tables application and is now visible in the Field Properties dialog in Input/Library Data applications when appropriate (not with system or required field).
3. For Range Filters to work in the Output application group, the field type for the "Range Top field" and "Range Bottom field" must be numeric. Text fields will cause the filter to fail.
====================
6.1.022 12Apr2004
====================
1. Maintenance release.
====================
6.1.021 28Mar2004
====================
1. Maintenance release.
2. The system fields LibFile and LibFileSpec have been added to the other system fields already supported for evaluation when printing or previewing in the Drawing Library and General Drawing applications and their associated block applications.
====================
6.1.020 02Mar2004
====================
1. 019 broke the Site Layout button in Output applications. This build fixes that problem.
2. For those that have received our AGS files since about August of 2003, either by downloading from our Web site or from us as new clients, there may be a mistake that causes the rock colour data not to print. To fix:
A. Go to Data Design:Library Data.
B. Change the table selection list in the toolbar to BSI ROCK DESCRIPTION. If it is not in your list, you do not have the files that are a problem. There is nothing more to do.
C. The Data Expression for the "Colour" row should be:
<<STRATA ROCK.Colour>>
The erroneous version is:
<<STRATA ROCK.Colour Main>>
We have reposted the files with this correction.
3. Database Design: System fields can now be marked Calculated (Read-Only). Formerly the checkbox was hidden for these fields. This includes the North, East, Elevation fields in the POINT table as well as many others in the Lab Testing tables.
4. The AGS Checker was part of the gINT update installation. It has now been separated out into its own update. See www.gintsoftware.com/support_updates_agschecker.html.
5. Clarification: Blocks in graphic tables can only contain expression variability on a project or prompted report variable basis. Expressions in blocks in these reports are only evaluated once per output run.
====================
6.1.019 19Feb2004
====================
1. Maintenance Update.
2. gINT Rules: The RecordCount property of recordsets generated from the OpenRecordset method of databases may not be accurate without first moving to the last record. We missed this in the GR005 sample on our Web site. In the InclinometerInitialize procedure of the GR005 module:
Set snDepths = gINTRules.CurrentProject.OpenRecordset(sSql, dbOpenSnapshot)
With snDepths
If Not .EOF Then
glNumRows = .RecordCount
the code needs to move to the last record before setting glNumRows. That is:
Set snDepths = gINTRules.CurrentProject.OpenRecordset(sSql, dbOpenSnapshot)
With snDepths
If Not .EOF Then
.MoveLast
glNumRows = .RecordCount
.MoveFirst
We have changed GR005 on the Web site. You can redownload or just insert the .MoveLast and .MoveFirst lines as above.
====================
6.1.018 08Feb2004
====================
1. By default the ComponentLegend function formats the output with the "label =" right justified on the specified X value for the entity and the description right of that X value. This applies only to left justified text. This behavior can be overridden by inserting a ", <some number>" as the second parameter:
<<ComponentLegend([MY TABLE],0)>>
This second parameter is optional. If blank or non-numeric, the default behavior is used. A non-zero value inserts a tab at the beginning of each legend line and tabs to that position relative to the entity X. The value must be in page units, that is, inches or millimeters, as appropriate to the report. The value can be negative.
2. In Data Design:Project Database and :Library Tables, on merging fields from another table, either in the current database or an external file, previously the program merged in all the fields from the selected table that were not replicated in the current table. Now the program presents you with the list of fields that can be merged and you can select the one or ones you require.
3. Support for the ReportKeyList system field has been expanded to text tables and graphic text documents. This gives the list of the data keys that were actually used on the output. That is, it takes account of any specified range list, filters, output conditions, and missing data. The format of the field is such that it can be used in the "In" clause of an SQL expression. See the existing documentation on "ReportKeyList" for details of usage.
4. The "Extension of Column Lines below body" property under the "Columns and Lines" tab of Log Report properties not only extends column lines on column entities but also appropriately offsets the line drawn at the bottom of the log body, if that property ("Bottom of Body"; also in the "Columns and Lines" tab) is marked.
5. The "Extension below body" property for vertical lines to depth entities extends these lines into the footer by the amount specified.
6. If you start gINT by double clicking on a project file in Windows Explorer, if the path is a "long file name", gINT shows the file name converted to DOS 8.3 format. If you then repair and compact the file the new copy has the 8.3 name. The problem is in the file association definition. This was improperly set up by the gINT installation program. We have repaired the problem for new clients. It is an easy fix for existing installations if this is a problem for you:
A. Open Windows Explorer
B. Select Tools: Folder Options... from the menu.
C. Select the FileTypes tab. Wait for Windows to complete its search.
D. Type a G to start your search for "GLB", "GPJ", and/or "GSC"
E. Repeat pressing G until one of the above is highlighted.
F. Click the Advanced button.
G. Click Edit... You will see the word "open" highlighted.
H. Press Tab. The next box will have the highlight. It will show a path to gint.exe, followed by %1.
I. Press Home. The caret should be at the start of the text.
J. Type a double-quote character ".
K. Move the caret to just after gint.exe.
L. Type another quote.
M. The line should read "x:\...\...\gint.exe" %1. For example:
"C:\Program Files\gint\gint.exe" %1
Note that %1 is outside the quotes.
N. Click OK
O. Click OK again.
P. Click on the highlighted line.
Q. Press the Down arrow to move to the next gINT association.
R. Repeat.
S. Click Close.
====================
6.1.017 11Jan2004
====================
1. With Table Lines Horizontal entities in Graphic Table reports, the Extent property choice "Only below last line with data" will print a horizontal line below the last line with data. That is, only one line will be printed per output.
2. Find/Replace in Input: A number of problems relating to special situations with this facility have been fixed. If you had experienced problems in the past, please retry these commands. If problems still exist, please report them.
3. AGS Checker:
A. Allows selection of the choice of message listings: By scan group, line number, and/or severity.
B. Adds line numbers to a number of messages classes that originally did not state the line number.
4. On some log forms the vertical lines between columns extends into the footer some distance. That is, a gap is left between the bottom of the body. If the form is using polylines for the column lines, this is not an issue. The lines are merely drawn to the required vertical coordinates. If the form uses vertical lines to depth entities for the lines between columns, by default the lines terminate at the bottom of the body (top of the footer) when the lines extend across pages. On the last page they terminate at the specified bottom depth. To extend these lines into the footer, the vertical lines to depth entities have the property "Extension below footer". Supply the appropriate value (must be greater than 0) in this property.
If the log form uses column entities, you can set this extension value in the page properties of the report. Under the "Columns and Lines" tab supply this value in the "Extension of Column Lines below footer" property. All column entities will then use this value.
5. gINT Rules Samples on Web Site (www.gcagint.com/gint_rules_samples.htm)
A. The comments at the top of each procedure in the GR005 module stated that the procedures needed to be referenced in the "gINT Rules Pre-process on Save" property. The correct property is "gINT Rules Procedure on Empty Dataset". Also, some of the comments referred to the "probe" table when then should have referenced another table. We have corrected those comments and reposted GR005.
B. GR008 did not work properly on executing the gINT Rules:Recalculate Current Table command or on import. This gINT update corrects those problems.
====================
6.1.016 05Jan2004
====================
1. gINT Rules
A. Method of gINTRules.GridData object:
Name ReadingsListLoadFnB
Arguments ListName As String
ReadingsField As String
Optional NameField As String
Optional CompactOnSave As Boolean
Returns True if failed to obtain data for any reason, that is, list not found, either of the specified fields not found, data not found in the specified list.
Description
This populates the current grid with the contents of the specified readings list (Data Design:Readings Lists application). The data in the readings list "Reading" field are inserted into the field name specified by the "ReadingsField" argument. Optionally you can also populate a field specified by the "NameField" argument with the contents of the "Name" field of the readings list. By default, the program will compact the grid on save by removing all records where there exists data in just the "ReadingField" and "NameField". Set to "CompactOnSave" argument to "False" if you do not want the grid compacted. See the next item (Library Lists) for a method of specifying the readings list to use. See the code procedure (SieveInitialize) for the SV READINGS table in the GR005 gINT Rules sample code on the Web site (www.gcagint.com/gint_rules_samples.htm) for an example of the use of this method.
Sample usage
With gINTRules.GridData
If .ReadingsListLoadFnB(sMyReadingsList, _
"Sieve Size", _
"Sieve Name", _
True) _
Then
MsgBox "Unable to load Readings List '" & sMyReadingsList& "'." & vbCrLf & _
"Either it doesn't exist or is empty." & vbCrLf & _
"Check Data Design:Readings Lists for a valid list."
End If
End With
B. The "GintRecID" field is a hidden long integer value that is used by the program to keep track of data that are being edited. In the Input and Data Design:Library Data applications, each row has a GintRecID value. If it is a new row, the GintRecID is 0. For an existing row the number is greater than 0 if no changes have been made in the editing session or less than 0 if modifications were made. On saving, all the GintRecID values become unique values greater than 0.
You can use this value to determine if a row has been changed or is new and perform different actions. For example:
iPsGintRecID = gINTRules.GridData.FieldCol("GintRecID")
For lRow = 1 To glNumRows
Select Case Val(gsDataA(iPsGintRecID, lRow))
Case Is < 0
'Existing record that has been modified.
...
Case 0
'New record.
...
Case Else
'> 0. Existing record that has not been changed.
...
End Select
Next lRow
Note that when data are imported, the GintRecID field is always a number greater than 0 by the time the gINT Rules code is executed. Therefore, the above code will never execute the first two cases on import.
See the code procedure "LastModifications" under the GR008 COMMON PROCEDURES module in the GR008 gINT Rules sample code on the Web site (www.gcagint.com/gint_rules_samples.htm) for an example of the use of this field.
2. The Lookup property of fields allows the selection of "Library Lists". Currently the only one supported is "Readings Lists". This list has its "Must use Lookup" property marked by the program and this property cannot be unmarked. This list will show all the items defined in the Data Design:Readings Lists application. Its main purpose is to allow writing a gINT rule that will populate a grid with the contents of a selected list. See the code procedure (SieveInitialize) for the SV READINGS table in the GR005 gINT Rules sample code on the Web site (www.gcagint.com/gint_rules_samples.htm) for an example of the use of this lookup.
3. Field Rules
A. We did not allow specification of field rules for Read-only field and the POINT table system fields HoleDepth and Plunge. These restrictions have been removed so that field rules can now be assigned to these items.
B. We did not allow specification of both the "Decimals displayed" and "Round to nearest" rules for numeric fields. This can now be done.
4. The <<DMK!xx>> instruction in a text entity outputs a data marker by the specified name. On graphs whose "Graph Data Sets" property (under the "Data Representation" tab) is set to anything other than "All data items", data markers with numeric names (1, 2, etc.) are limited to the maximum number of data sets on the graph. This is to allow variable legends. You could set up legends that show the data markers for each set for up to 20 sets, let's say, but only 10 are printed. This behavior would suppress the printing of <<DMK!11>> to <<DMK!20>>. Data markers with non-numeric names (ABC, A2B, etc.) are not affected by this behavior and will always print.
When used on graphs that have "Graph Data Sets" set to anything other than "All data items", <<DMK!2>> will not necessarily print what you see as the data marker named "2" in Symbols:Data Markers. It will print the data marker associated with the second plotted data set which could be something other than data marker "2".
5. The system fields <<DrawingFile>> and <<DrawingFileSpec>> appear in the Items list in the data tool in all applications. However, remember that they only have use on general drawings so only use them in applications that will ultimately be output to a general drawing file.
6. You can use the F2 function key to launch the dialog for Bitmap, gINT Drawing, and Any file fields in Input.
7. On multiple graphical text document pages per sheet (graphical text document report properties dialog), the "Fill Order" property allows you to fill the page vertically (the default) or horizontally. Vertically will fill the upper left position and fill down and then move a position right and start at the top again. Horizontally will fill the upper left position and fill right and then move a position down and start at the left again.
====================
6.1.015 16Dec2003
====================
1. gINT Rules:
A. The "gINT Rules Procedure on Empty Dataset" executes when the empty grid gets focus. For main grids this means the code is fired when the screen is first displayed, as the grid is given focus when it is shown. For child grids, however, focus is not granted unless there is some data in the parent record. The parent records does not have to be saved, but the grid row has to exist as evidenced by the addition of an empty row under the newly populated row. This means that if you have specified code to prepopulate the child grid, you fill in any fields in the parent that may be needed for your code to decide how to proceed when adding the child data. For example, in a particle size distribution split screen, the parent might contain a lookup list that specified which sieve set was used. On setting focus in the child grid your prepopulation code reads that field and provides the appropriate sieve sizes.
B. Property of gINTRules.GridData object:
Name ParentGridData(FieldName as string)
Type String
Usage sMyData = gINTRules.GridData.ParentGridData("MyField")
Read-only
You can extract any data field from the parent. This property always has data from the grid. If there is no parent grid it returns empty. The following returns the same result:
sMyData = gINTRules.GridData.ParentRecord.Fields("MyField")
however, in the case where you are prepopulating a child grid based on some value in the parent grid, the ParentRecord object does not work. ParentRecord is a recordset and is populated from the database. On prepopulation of a child grid, the parent may not yet be saved and therefore a ParentRecord recordset cannot be created. Even if the parent record is saved, the user may have made changes to the parent data in the grid so the results from the ParentRecord would not be accurate.
C. Property of gINTRules.GridData object:
Name ForeignKeyValues(Optional KeyName or KeyNumber as Variant)
Type String
Usage sAllKeys = gINTRules.GridData.ForeignKeyValues()
sPointID = gINTRules.GridData.ForeignKeyValues("PointID")
sPointID = gINTRules.GridData.ForeignKeyValues(1)
Read-only
If a field name is provided, returns the value.
If an Integer or Long Integer constant or variable is provided, the value at that position is returned.
If no parameter is passed a comma delimited list if all values is returned.
If the supplied parameter is not a valid number or string, returns empty.
This property should be used instead of .ParentRecord or .ParentGridData for key field values.
D. When running gINT Rules in the code window (F5 or clicking on the "start/resume" button in the toolbar), the program needs to know which procedure name to pass to your code. It uses the following logic while looking in the properties of the grid that has focus:
1. If there are no data in the current grid, it passes the procedure name in the table properties for gINT Rules on Empty Dataset. If that property has not been specified no procedure name is passed.
2. If there are data in the current grid, if there is a property supplied for "Pre-process on Save", that procedure name is passed. Otherwise, if there is a "Procedure on Save", that procedure name is passed. If neither exists, no procedure name is passed.
3. If one of the above situations results in no procedure name being passed, or if you wish to set your own procedure name, do the following:
a. Put a breakpoint on the line that calls the procedure. Usually:
CallByName Me, gINTRules.ProcedureName, vbMethod
You make the line a breakpoint by either putting focus in the line and pressing F9 or clicking in the gray area left of the line.
b. Run the code by press the F5 key or clicking the start/resume button (right facing triangle in the toolbar).
c. Execution will halt on the breakpoint. Click in "ProcedureName" in that line and press Shift+F9 or click the "evaluate expression" button in the toolbar (spectacles). This will open the Immediate Window at the top of the form and print either:
gINTRules.ProcedureName -> "No code procedure name specified for table 'XXXXXXX'."
(where 'XXXXXXX' is the table with focus.)
or
gINTRules.ProcedureName -> "XXXXXXX"
(where "XXXXXXX" is the procedure name passed by the program).
d. Remove the "->" and all text right of this and supply the procedure name you wish to use following an equal sign. For example:
gINTRules.ProcedureName = "MyProcedure"
and press enter.
e. Continue execution by press F5 or clicking the start/resume button.
This supplied procedure name will remain in effect as long as focus remains in the code editor dialog.
E. When gINT Rules and Field Rules are both used, the program executes the gINT Rules first and then checks Field Rules. This can take some programming burden off of gINT Rules. For example, you could write gINT Rules code that checks that values are between certain ranges and then format them to a certain number of decimal places. Instead, you can put those specifications in Field Rules. Besides being faster and easier, this also gives the user the ability to make changes to these parameters without changing the gINT Rules code.
This order is followed whether data are manually input or they are imported.
2. In the Table list of the data tool graphical codes are listed at the end of the table list, that is, under the project database structure specified by the data template, any library tables, user system data, and report variables. These are for material, sample, well, etc. graphics. The field list for these items contain only "Name" and "Description". This allows you to paste in <<MATL.Description>> into an expression.
3. If you wish to place multiple graphs on a page you can export all graphs to a single gINT Drawing (GDW) file by selecting the "Merge" option on the export. To aid in placement, the graph report properties:
Frame Offset X
Frame Offset Y
can be used to place the graph frames and associated entities (those with the "Placed on Graph Frames" property marked) at varying locations. These properties are under the "Data Frame" tab and can be expressions. Note that only one set of offsets can be used for any output run, that is, the first page can't have a different offset than the second, etc. Therefore, the expression can only be a project or system level expression. A system level might be based on a graph report variable or some system level variable like <<DXFExport>>.
4. The system data items DrawingFile and DrawingFileSpec work only in general drawings and general drawing blocks. They report the gINT Drawing file name and full path and name, respectively. These two items only appear in the data tool in the two general drawing applications. However, you may have reports that are always exported to a general drawing and you wish to have these items appear on the final general drawing. You can embed these items in your reports and the output process will pass them through unchanged, that is, in the general drawing you will see <<DrawingFile>> or <<DrawingFileSpec>>. That is, these items are temporarily evaluated when outputting but always remain in their original state. This also means that if you preview, print, or export the report to anything except a gINT Drawing file you will see the name of the temporary gINT Drawing file that is created during the output process.
5. The graph report "Curves from Equations" (under the "Data Representation" tab) presents a grid dialog where you can specify as many curve equations as you wish. You can specify an Output Condition for each curve. This can signicantly reduce output time for suppressed, complex curves with many data points. For example, you have a report variable called "Output Curve" that has a value of "X" assigned to it in the report. At output time the user either leaves it to output the curve or deletes the "X" to suppress it. You could write your equation as:
<<HasData(<<Report Var.Output Curve>>,_
...your expression here..._
)>>
However, the program will still evaluate your expression for as many times as you have specified in the number of points (Num Pts) property of the curve, even if you have cleared the report variable. If instead you put in the Output Condition of:
<<HasData(<<Report Var.Output Curve>>)>>
If "Output Curve" is blank, no evaluation of the curve expression is performed.
6. In Data Design:Library Data and :Lookup Lists, the File:Import/Export:Export Data to Excel and :Export Data to CSV menu items give the choice of exporting the current table, all tables, or selected tables. In the case of Excel export you can also launch Excel after export.
7. Export of log and fence reports to DXF that have the "Retain Layering" property marked requires that the DXF export is set up to export one file per page (property is under the File:System Properties dialog under the "DXF Files" tab). However, the program now automatically switches to one file per page if "Retain Layering" is marked. Previously, if the "Multiple Page Output to Separate Files" property was not marked, the "Retain Layering" property was ignored.
8. New system data item: <<FenceEquallySpaced>>. Applies only to fence reports and returns True if the fence posts are set to be equally spaced using the "Equally space points along distance axis" property at output time. Will return False even if this output property is marked if the output is in 3D since the output property only applies to two dimensional views.
9. In Output:Fences, the "Equally space points along distance axis" will equally space the fence posts across the data frame. This property is a check box and is located within the main output specification screen. It only applies to two dimensional views. The order in which the boreholes will print is the same order that they would have printed without the property marked. When selected, this property will also turn off the top and bottom division numbers and the vertical grid lines.
Let's say you have a report that has the distance axis label "Distance Along Baseline". Since the distance axis has no meaning with fences where the points are forced to be equally spaced and the division numbers are not printed, you will probably want to suppress this label with equally spaced points. To do so, write the following in the "Output Condition" property of the text entity:
Not <<FenceEquallySpaced>>
That is, don't output if the points are equally spaced. Note that <<FenceEquallySpaced>> will return False if the view is in 3D, even if the property is marked.
10. Column Width Expression in Depth Text and Depth Text Column entities: This property is used for the text wrapping width only with horizontal text (Angle = 0 or blank). If the text is not horizontal, no wrap width is used and this property is only used for the column definition which can be used for drawing boundary lines.
With other text entity types with this property, angled text is wrapped to this value.
11. We have update the gINT PDF driver with a new version. This fixes problems with complex bookmarks using certain types of reports. It also fixes some problems with proper export of oversized page sizes.
12. The AGS Checker program:
A. Additional checks were put in place.
B. Better documentation of certain conditions.
C. If the number of messages is 10 or more, the program now prints two more lists of the messages, one sorted by line number and one by severity.
====================
6.1.014 10Nov2003
====================
1. We discovered a corruption introduced in 6.1.011. Under very special conditions when outputting data from a database on your network it was possible for the program to crash and reboot the system. Where it did occur only did so under Windows XP. This problem has been fixed.
2. Polylines that cross themselves will not export to DXF files. For example, a figure "8". On exporting to DXF the clipping procedures cannot deal with the crossing and the polyline is exported unfilled. No problem with preview, print, or exporting to any other file format. The solution is to restructure the symbol into multiple filled polylines so that the crossing is elimiated.
3. gINT Rules:
A. After running a gINT Rules Empty Dataset procedure, if rows have been added, the change flag will be set according to the programmer's setting of gINTRules.GridData.ForceSave. By default the change flag is not set so that if you leave without making any changes the added rows are not saved. Generally this is what you want to do but there are rare cases when you want the save to occur. In that case add the statement:
gINTRules.GridData.ForceSave = True
B. Ctrl+Tab within the gINT Rules dialog switches between the List and Code windows.
4. Read only property on fields: Previously the "Do not display" property was disabled when the Read only property was set. That has been changed so that you can hide read only fields if you wish.
====================
6.1.013 03Nov2003
====================
1. When specifying graphics on reports via the Bitmap File and gINT Drawing File fields, the paths to the specified external files are stored in your project database. If you send the project to another office, you must also include the external files for proper output. However, the new office may not put them in the same folder or folders and they may not be able to, that is, they may not have the same specified drive or drives. They could go into your database and change all the references appropriately. However, there is no need. The program looks for the files in the follow order:
A. In the specified folder.
B. In the current project folder.
C. In the default project folder specified in File:System Properties.
D. In the default data template folder specified in File:System Properties.
E. In the path where the gINT program resides.
So if the new office moves the external files to one of these location, the program will find them.
2. gINT Rules:
A. Added support for running a gINT Rules procedure upon entering a grid screen where no records exist for the current dataset.
B. The ParentRecord object of the gINTRules.GridData object is both read and write. The original documentation stated that it was read only.
C. Maintenance changes to address issues brought up from users.
====================
6.1.012 27Oct2003
====================
1. gINT Rules:
A. gINT Rules code now works on the Project table.
B. You can add rows to the data array and they will be saved to the grid.
C. The hidden key fields in the grid will now be returned properly. This did not work. For example, you wish to retrieve the PointID value. That would be done like the following:
iPsPointID = gINTRules.GridData.FieldCol("PointID")
sPointID = gsDataA(iPsPointID, lRow)
D. The gINT Rules ParentRecord property was not populated for one-to-one children. It now supplies the eventual one-to-many parent up the chain. For example, the ATTERBERG table in Lab Testing is a one-to-one child of Lab Specimen. If you request the ParentRecord the Point record will be returned by the property. If the table has no parent an invalid object will still be returned.
E. In the built-in gINT Lab Testing tables, both is your project database and library two tables (HYDROMETER CALIBRATIONS and LOAD RINGS), there is gINT Rules code that is executed by the program. You do not have access to this code. However, you may wish to perform some data manipulation before the native gINT procedure is executed and/or afterwards. In the table property dialog of lab testing tables that have a native code procedure, you will see three properties:
gINTRules Pre-process on Save
Native Code Procedure on Save
gINTRules Procedure on Save
The "Native Code Procedure on Save" is the name of the internal gINT procedure. This is a read-only field. You would specify your procedure in either the "gINTRules Pre-process on Save" and/or "gINTRules Procedure on Save" properties. In tables where is no native gINT procedure, only the last property is shown.
2. We have changed the method with which we calculate the compaction test maximum dry density and optimium moisture content to use a variation of our cubic spline curve fitting method. Extensive testing has shown it to work better than the parabolic fit we had used earlier. At the same time we have found that the differences between the two methods are generally small. Further, this new method will match the new unadjusted cubic spline vs. independent axis graph line option. Therefore, the calculated result will match the plotted curve.
Note that the calculation of the maximum and optimum in the compaction test only occurs if you have inserted the boolean field "Do Not Calc Max Opt" in the parent compaction table.
The usual disclaimer applies to this capability: soil testing results, especially compaction tests, are open to interpretation. Our methodology may not be correct in the judgement of persons reviewing the work. It is your responsibility to double check the results and make adjustments if you deem them necessary.
3. The two graph line options (Data Representation tab in the graph reports page dialog), Cubic Spline vs Ind (unadjusted) and Cubic Spline vs Dep (unadjusted), work exactly like Cubic Spline vs Independent Axis and Cubic Spline vs Dependent Axis except that internal adjustments that the code makes under certain geometric conditions are not implemented. We recommend using the Cubic Spline vs Ind (unadjusted) option for compaction curves.
4. Site Map application in Input:
A. If you have a number of entities overlapping a Point ID entity it may be difficult to click on the Point ID entity to drag it. In this case you can right click and drag the Point ID entity. In drag mode, with the right mouse button depressed, only Point ID entities will be selected.
B. The File:Lock/Unlock Layer menu item renders all drawing entities uneditable. You can add new entities to the site map when the layer is locked but cannot edit. The PointID entities are not affected by this mode. When the drawing layer is locked, you can click and drag on PointID entities without inadventently selecting drawing entities. Instead of using the File menu, you can also click on the lock button on the main toolbar to lock and unlock the drawing layer.
C. To add a new PointID to the project (PointIDs:New PointID menu item), you first specify the location by clicking on the drawing or typing the coordinates (east,north). Then a dialog will appear with the POINT table fields. The North and East coordinates will be populated with the specified location coordinates.
5. In the Lookup property of text fields, the graphic lookup for data markers has been added.
6. You can specify a line be drawn at the hole depth within a Text with Depth or Text with Depth Column entity using the three line at hole depth properties within the "Boundary Line" tab of the entity properties dialog. A line will be drawn at hole depth if the "Line at Hole Depth Type" property is set to any line type except "None". A line can be drawn at hole depth whether there is a boundary line specified or not. This line acts like other boundary lines in that it will bend down to avoid overwriting text that is output by the entity. If there is a bottom boundary line drawn at the same depth as the hole depth, the properties of the line at hole depth are used instead of the bottom boundary line properties.
Note that all column entities have their line at hole depth properties under the "Column Lines" tab. The Text with Depth Column entity is the exception with these properties under the "Wrap" tab to be consistent with the Text with Depth entity.
Sample uses for the line at hole depth:
A. You only want a line at the hole depth within a column. In this case you could also just specify the "BL Depth Expression" as <<POINT.HoleDepth>> and specify the thickness and color properties for the boundary line.
B. You have boundary lines through the column at various depth specified by the "BL Depth Expression" that may or may not draw a line at the hole depth (for example, sample boundary lines) and you want to ensure that a line at the hole depth is drawn. You could create a separate Lines with Depth entity to do this but that line would not bend if text spills below the hole depth.
C. You have boundary lines through the column at various depth specified by the "BL Depth Expression" that will definitely will definitely draw a line at the hole depth (for example, lithology boundary lines) but you want the line at the hole depth to have certain line color and thickness characteristics. You could also use the override boundary line color and thickness expressions to specify a different color/thickness at hole depth (for example, <<IIf(<<LITHOLOGY.Bottom>> = <<POINT.HoleDepth>>,0.02)>>.
In all sample uses there are ways to achieve the same effects as the line at hole depth properties but they are either more difficult to implement and/or not as flexible.
7. The "Border" tab of the Bitmap Symbol, In Place Bitmap Symbol, and Bitmap Symbol vs Depth entities provides properties to draw a line around the bitmap. The properties are:
Line Type
Thickness
Line Color
Offset Left
Offset Bottom
Offset Right
Offset Top
The Line Type, Thickness, and Line Color are the usual polyline properties. If no offsets are given, the program will draw the border around the extent of the bitmap. If you have white space around the edges of the symbol, these will be enclosed in the border. Left and right offsets are positive to the right, negative to the left. Top and bottom offsets are positive up, negative down.
====================
6.1.011 12Oct2003
====================
1. AGS Checker: Put in warning messages if the description field was missing from one of the meta-data groups or the description field was missing values. These groups are:
CODE (CODE_DESC)
ABBR (ABBR_DESC)
UNIT (UNIT_DESC)
FILE (FILE_DESC)
2. The "gINT Drawing" field type allows you to store references of gINT Drawings in your project fields. For example, you might wish to draw a test pit sketch for each test pit in a project. You could have a field called "Test Pit Sketch" in your POINT table of the gINT Drawing type. You would then create a gINT Drawing file in Drawings:General Drawings. There you would create your sketches, one drawing page per test pit. Name the pages whatever you wish but naming them by the test pit names would probably be best. In Input you would click the browse button [...] right of each grid cell under this field, select the file and then the page associated with each test pit. Optionally you can also give a description. The description is a memo-type field so you can type as much as you wish.
On your report you would specify a discrete graphic entity with the Discrete Graphic property specified as:
<<ProjectSymbol(<<POINT.Test Pit Sketch>>)>>
This will extract the file and page name from the appropriate field in the project. The rest of the properties in the discrete graphic entity work the same as with any other discrete graphic entity that takes its specification from Symbols:Discrete Graphics.
You can also draw sketches on a depth basis by using the Discrete Graphics vs. Depth entity (logs and fences only).
The files referred to by these fields remain on disk, they do not become part of your gINT project. However, when output, the entities are transferred from the source files to the gINT drawing that is created at output. So if you save to a gINT Drawing file, these external entities will be stored in these files and therefore the original source files are not referenced by the final gINT Drawing file.
If you have gINT Logs, you can use this field type but cannot generate the gINT Drawing file. The Drawings:General Drawings application is not available in gINT Logs.
3. The "Any File" field type allows you to access virtually any file from within your gINT project in Input. For example, you might store your project report in a Word document and scheduling in an Excel spreadsheet. You could add two fields in the PROJECT table, let's call them "Project Report" and "Project Scheduling". Assign the "Any File" field type to them. With this type, you will be asked for the file extension (doc and xls, respectively for these two types). You can give multiple extensions by separating them with commas. For example, AutoCAD can open both DWG and DXF files so you would specify "dwg,dxf" for the extensions. Optionally, you can also supply the application description. This property is not used by the program and is for internal documentation only.
The extensions specified must be registered on your systems. When you install Word or Excel these products automatically register their know extensions with your system. If the extension you wish to use is not registered with any application, you must do so manually for this to work. You can do so in Windows Exporer, under the Tools:Folder Options menu. Click on the "File Types" tab to make your registration.
If you specify multiple extensions, the program uses the first in the list. If you specify no extension, the program uses the extension of the file that you specify to determine which application to launch.
In Input, when in an "Any File" field type, click the browse button [...] right of the field and a dialog with three properties appears:
Specify File: Use the browse button [...] right of this field to specify which file you wish to access.
Description: Optional description of the file. This is a memo field so you can type as much as you wish.
Launch Application: This is a read-only description field describing the application with a launch button [...] at the right. Clicking on this button will launch the associated application and bring up your specified file. If there is no specified file, the application is still brought up.
These fields only store the name and paths of the files and their descriptions. The files themselves never become part of the gINT project.
4. If you have a discrete graphic or bitmap symbol entity in the design application and either:
A. the symbol is variable and cannot therefore be shown at design time or
B. you have specified "None" for the "Design Mode Color" property (discrete graphic) or didn't mark the "Show at design time" property (bitmap symbol)
then a 0.2 inch (5mm) dotted line square will appear near the entity marker at the appropriate alignment. This square aids you in selecting the entity, that is, clicking within the square will select it.
====================
6.1.010 09Oct2003
====================
1. A bug was introduced in 009 that caused certain operations in Lab Testing to stop working. This update fixes that problem. Our apologies for the inconvenience.
====================
6.1.009 07Oct2003
====================
1. Mainly a maintenance update.
2. In Reports:Logs, the Log:Build Columns:Build Column - Plot vs Depth and :Build Column - Bar Chart vs Depth menu items will convert a plot vs depth entity to a plot vs depth column entity and a bar chart vs depth entity to a bar chart vs depth column entity, respectively. Unlike the other build column commands, these only map the main entity to the new column entity.
====================
6.1.008 30Sep2003
====================
1. You are in the middle of a multiple step command in a gIDraw application (for example: move, copy, erase, build column entity) and you invoke another command before completing all the steps. The original command is terminated and the new command takes place. However, if you invoked a view command, on completion, the original command (with some exceptions) will be continued from the point at which you left off. For example, you need to move a number of entities and in the process of selecting those entities you realize that some are off the top of the screen. You pan the screen down to see those entities and the move command will then continue with the entities that you have already selected being marked.
The view commands that behave in this manner are:
Refresh
Pan
Zoom Window
Zoom Previous
Zoom Extent
Zoom Page Outline
Zoom Out
Zoom In
Zoom Times
Quick Zoom
The scrolling buttons at the lower right of the screen (and their keystroke short cuts)
You can invoke a number of these view changes, and in any combination, within a multiple step command. For example, you might have to pan a few times to get the view you need.
If the original, multiple step command that is interupted by a view command has an initial dialog, on returning to the original command from the view command, the dialog will be brought up once more. The one exception is the Copy Properties command which will continue normally.
If the command is interupted in the middle of a step that has a rubberbanding feature, on continuing the command after the view command, the rubberbanding will be gone. You can still continue successfully but without the benefit of the rubberbanding. For example, you have selected the handle point on a move or copy command and are prompted for the final location of the handle point. As you move the mouse a dashed line anchored at the handle point follows your mouse movements. At this point you then pan the screen. After the pan you are still in the proper configuration for completing the move command but you will not see the dashed line.
Some multiple step commands do not support this feature and invoking one of the above view commands will terminate them. This group includes most of the polyline drawing and editing commands. The ones that work with an interupting view command (a shorter list than those that don't) are:
Extend Polylines
Close Polylines
Trim
Replace PLines
Replace PLines with Points
Offset PLines
The other group of commands that do not allow interupting view commands are the few mutliple step view commands themselves: Pan and Zoom Window. That is, if you have selected the first corner of a Zoom Window and then clicked the Zoom Previous button, the Zoom Window command is terminated.
2. On some systems, the drop down lookup lists in the Input and Library Data applications did not work properly when typing in the text box. This problem goes back to version 5. We believe we have fixed it. Please let us know if you encounter any problems with it.
3. The Axis Scale property under the Independent and Dependent tabs in the graph report properties dialog can be an expression. However, like the Min and Max values, the scale is only evaluated once per output run, that is, all pages will have the same value, it cannot change on a specific page within an output run.
4. In the main tab of the report page properties dialog in logs, graphs, graphic tables, and text tables are the following properties:
Sort Field 1 (<<TABLE.Field>>)
Sort Field 1 Descending
Sort Field 2 (<<TABLE.Field>>)
Sort Field 2 Descending
These are the same properties that appear on the output screen for these report types. These fields allow you to store sort information with the report. When the report is brought up in the output screen, the program inserts these values into the corresponding controls on the screen. You are then free to change them for a specific output run.
The sort field properties must be in the form <<TABLE.Field>>. We recommend using the data tool to paste in the value instead of typing it.
These properties cannot be changed in the page properties dialog at output time. It would do no good. These properties are only read by the program when the report is first brought up in the output screen.
5. The PointID,Depth,Reading,ItemKey key set can be used to create tables that are children of lab testing tables that give additional information for each reading.
6. In AGS export, entries to the ABBR table can be built from project table lookups, that is, tables within the source project that have an ItemKey keyset. Like library table lookups, you must have a field named "Description" for this to work.
7. The "Override Fill Color Expression" of polyline entities allow you to write expressions to generate fill colors based on some criteria. This overrides the "Override Fill Color" property where you can only pick from a list.
8. The Data Marker Color Expression properties under the "Override Line/DM Expressions" tab of the graph report properties dialog allow you to write expressions to set data marker colors for each of the six dependent variables. For example, let's say you are generating a graph of N Value vs. Depth and you want the data marker color to be tied to the layer in which the data was taken. Using the AGS database structure, there is a field in the GEOL table called GEOL_GEOL. Let's say we had values in this field called "A", "B", "C", and "D". In the "Data Marker Color Expression 1" property we would write something like the following:
<<Case(<<SqlRange(_
<<Depth>>,_
[GEOL].[GEOL_GEOL],_
[GEOL].[GEOL_BASE],_
[GEOL].[Depth],_
1_
)>>,_
= "A",255,_
= "B",16711935,_
= "C",49152,_
= "D",8421376,_
)>>
The SqlRange function will retrieve the GEOL_GEOL value associated with the current depth. See the Help topic for SqlRange for details of its usage.
The Case function then assigns the appropriate color based on the GEOL_GEOL value. You can get the numbers from the Symbols:Colors application. You must use the color numbers, not the color names. The names are not used by gINT. You can change them to whatever you wish without affecting the actual colors because gINT stores the color numbers, not names.
If the GEOL_GEOL value is not in the list, the program uses the data marker color that is dictated by the other properties that affect data marker color under the "Data Representation" tab. These are "Data Marker Override Color" and "Set Data Marker color to line color". The order that the program uses for determining the color is:
Data Marker Color Expression
Set Data Marker color to line color
Data Marker Override Color
Native color of the data marker in Symbols:Data Markers
The above Data Marker Color Expression property will work for one project but now on another project you have different layer codes. You would have to change the expression to reflect the new codes. This is not a maintainable solution, especially if you are working on two or more projects at the same time. One solution is to create a separate report for different projects. Another horrible solution.
There are a number of very clever and complex methods of making this work in a maintainable manner. We will show one method which we believe is the best overall technique.
Set up a new table in your project database where we will store the layer codes for the project. Let's call it "LAYER CODES". It will have a key set of "ItemKey" and we will caption that field as "Code". Add two other fields called "Description" and "Color". The Color field will have the graphic lookup of Colors. The Description field is necessary to make a legend (see below) and for AGS export to properly populate the ABBR group with these codes.
In the GEOL_GEOL field, set the lookup property of that field to this project table. When you start a new project you will populate the new table with all your codes with their associated descriptions and colors. You will then pick from this list when in the GEOL_GEOL field.
The Data Marker Color Expression property will then change to:
<<Let(Layer Code = _
<<SqlRange(_
<<Depth>>,_
[GEOL].[GEOL_GEOL],_
[GEOL].[GEOL_BASE],_
[GEOL].[Depth],_
1_
)>>_
)>>_
<<Lookup(<<LAYER CODE.Color>>,<<Get(Layer Code)>>)>>
Now you would like to build a legend indicating which layers are represented by each color. This could be made up of one text entity that would give the layer code and, optionally, the description, and a solid-filled rectangular polyline with the fill at the appropriate color.
The legend text entity could have the following Text property:
<<Let(Layer Code = _
<<RecordItem(<<LAYER CODE.ItemKey>>,<<#>>)>>_
)>>_
<<ListBuildSepTrim(_
": ",_
<<Get(Layer Code)>>,_
<<Lookup(_
<<LAYER CODE.Description>>,_
<<Get(Layer Code)>>_
)>>_
)>>
This would be a repeating text entity. Under the "Repeat" tab of the properties dialog supply the appropriate values as follows:
Repeat Spacing: This would be a negative value if you wish each line to be below the previous line.
Number of Repetitions: Set a number greater than the number you believe you will ever have in a project.
Repeat Direction: Probably "Y", that is, vertical.
Repeat Variable Start: 1
Repeat Variable Increment: 1
The <<#>> in the text expression is called the "repeat variable". The above configuration will replace <<#>> with 1 and then 2, 3, etc. So the expression first retrieves the first layer code, then the second, etc. It then prints the code and description separated by a colon and two spaces (": "). If the entity runs through 10 repetitions and you only have 4 layers, the last six will not print anything.
Now for the filled rectangles. Create the same number of rectangles as the number of repetitions you specified in the text entity and lay them out so that they will be adjacent to the text. You would specify the following properties in each:
Output Condition: <<HasData(<<RecordItem(<<LAYER CODE.ItemKey>>,1)>>)>>
Fill Type[!Symbol]: Solid
Override Fill Color Expression:
<<Let(Layer Code = _
<<RecordItem(<<LAYER CODE.ItemKey>>,1)>>_
)>>_
<<Lookup(<<LAYER CODE.Color>>,<<Get(Layer Code)>>)>>
In the Output Condition and Override Fill Color Expression properties, the "1" is for the first rectangle. Use 2 for the second in these two properties, 3 for the third, etc.
The output condition ensures that a rectangle will not print if there are more rectangles than there are layer codes.
The above setup is maintainable, that is, changing codes in one place, the new LAYER CODE table, automatically changes the report.
9. When exporting to a GDW (gINT drawing file) format in Output, you can click on the "Open in General Drawings" check box under the file specification. This will open the exported file in the Drawings:General Drawings application on completion of the export.
10. When exporting to a CSV, XLS, AGS, TXT, or DAT file format in Output:Text Tables, or a TXT format in Output:Text Docs, you can click on the "View document after export" check box under the file specification. This will open the exported file in Excel (if it is an XLS file) or your default Windows text editor (WRITE or WORDPAD) on completion of the export.
====================
6.1.007 16Sep2003
====================
1. First public release of gINT version 6.