Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Chapter 3
Introduction
Project Management
Inside a Gemcom for Windows Project
Inside a Gemcom for Windows Workspace
Selecting a Workspace
Introduction
Using Gemcom for Windows will help you collect and organize large
amounts of data on a project-by-project basis. Each project is stored
on your hard drive in its own root directory which contains the
project database and other files associated with the project. This
root directory is also subdivided into a collection of multi-level
subdirectories for each main component of the project.
The project data is stored in the database file, where it is organized
into workspaces based on user requirements and the type of data.
The data stored in the workspaces, called the workspace data, is
then used by various Gemcom for Windows functions to generate
the working data that you will use and modify during your
exploration and solids modelling procedures. This working data,
which is stored in the various subdirectories of the project root
directory according to the function of the data, can be in a number
of forms, including extraction files, report files, plane definitions,
solids, surfaces, polylines, block models, status maps, graphics files,
etc. The working data and the workspace data are interrelated and
Exploration
Page 2020
Project
(Root Directory)
GCDBaa
General Data
Definitions, Profiles
(Files)
*.DAT, *.NDX
Session File
(File)
GEM4WIN.GES
Database
(File)
GCDBaa.MDB
(Subdirectories)
Drillhole
Traverse
Point
Polygon
Other
Workspace(s) Workspace(s) Workspace(s) Workspace(s) Workspace(s)
Working Files
and Data
Project Management
Gemcom for Windows automatically creates a suitable directory
structure on your hard disk when you start a new project. It
creates the project root directory and manages the multi-level
subdirectories and individual data files. You do not need to know
how the directory structure works in Gemcom for Windows because
the system handles the administration and directory navigation for
you. However, when you become more familiar with Gemcom for
Windows, it is useful to know about the subdirectories and file
names as well as how they are organized. See Appendix B: The
Project File Structure, Volume I: Core.
Page 2021
Exploration
Page 2022
Session file. This file keeps track of many of the settings that
were in use when you last exited from Gemcom for Windows.
Plane graphics files. These are the graphics files and grids
created to display your data on vertical sections, inclined
sections, plan views and surface maps.
Page 2023
Digitized data. These are the digizited data files that you
create with Gemcom for Windows.
Session File
Each time you exit from Gemcom for Windows, the program keeps
track of which project and workspace were active. It also
remembers a number of other program settings and options that
Exploration
Page 2024
Property record. This is the name of the project and the units
of measure in feet or meters for the coordinates.
Grids. These define the location and size of grids and their
relation to plans and planes.
Surface Topography
Surface topography information is stored in the Gemcom for
Windows workspace in a status map file (STATUSLN.DAT) as a
combination of digitized contour lines and feature lines.
Page 2025
Exploration
Page 2026
Graphs
All the data files created by the statistical analysis modules and
subsequently used by QuickGraf are placed in a special
subdirectory called \GCDBaa\GRAPHS.
Extracted Data
All the standard Gemcom Extraction Files that you create when
you extract data from a Gemcom for Windows workspace are placed
in a special subdirectory called \GCDBaa\EXTRACT.
Imported Data
All the data that you import into Gemcom for Windows is placed in
a special subdirectory called \GCDBaa\IMPORTS.
Exported Data
All the data that you export from Gemcom for Windows is placed in
a special subdirectory called \GCDBaa\EXPORTS.
Reports
All the reports that are directed to data files are placed in a special
subdirectory called \GCDBaa\REPORTS. Also, all the report format
definition macros that you define using either the quick-reporting
module or the report macro editor are stored in this subdirectory.
Page 2027
Templates
All the pre-defined workspace structure templates provided with
Gemcom for Windows, along with any other templates you might
want to create, are stored in a special subdirectory called
\GCDBaa\TEMPLATE.
Digitized Data
All the digitized data files that you create with Gemcom for
Windows are stored in a special subdirectory called
\GCDBaa\DIGITIZE.
Plots
Any plots files transferred from previous versions of PC-XPLOR
during the file conversion or installation process will be stored in a
special subdirectory called \GCDBaa\PLOTS.
Exploration
Page 2028
Fields
Records
Data
Values
HOLE-ID
NORTHING
EASTING
PCX-001
2325.8
2176.2
555.7
PCX-002
2417.6
2185.5
545.6
76.0
PCX-003
2437.0
2242.3
537.4
112.0
PCX-004
2479.1
2182.6
520.0
393.0
PCX-005
2495.7
2317.7
532.2
129.0
PCX-006
2500.5
2037.9
500.0
282.0
PCX-007
2522.8
2136.4
503.0
230.0
PCX-008
2531.4
2245.0
523.8
118.0
PCX-009
2537.1
2409.9
573.2
500.0
PCX-010
2578.1
2289.1
551.1
428.0
PCX-011
2582.6
2183.7
523.8
490.0
PCX-012
2590.1
2046.2
448.3
83.0
ELEVATION
LENGTH
445.0
Workspace Tables
Gemcom for Windows workspaces are organized into tables
containing data. Each workspace must have at least one or two
tables depending on the type of workspace, and can have a virtually
unlimited number of tables. Each table can be viewed as a grid
consisting of rows and columns, in which the rows are called
records and the columns are called fields. Within each table, every
field has its own field name and set of attributes. Data is entered at
the intersection of a row (record) and column (field). Gemcom for
Windows workspaces can contain a maximum of 128 tables.
Workspace Records
Each row in a workspace table is called a record. Each record
consists of a number of fields. Workspace records do not have any
special attributes, while workspace fields have a few attributes.
Section II: Workspaces
Page 2029
Records are created when you add data to the workspace using any
of the workspace management tools for entering data. Records can
be added to or deleted from the workspace at any time.
Workspace Fields
Each column in the workspace is called a field. Workspaces can
contain a maximum of 255 fields. Data is entered into the
workspace at the intersection of each record and field. Each field
exists in every record in the table, even if data has not been entered
into the record or field. Fields are given a set of attributes which
define the type and range of data that can be entered into the field.
Data values for all the records in a table for a particular field must
fit all the attributes that have been defined for that field:
Azimuth
Closed
Comp-id
Composite
Dip
Distance
Feature
From
Hole-id
ID
Length
Location
Location-1
Location-2
Exploration
Page 2030
Point
Polygon
To
Trace-Type
Traverse
String (alphanumeric)
Memo (alphanumeric)
Integer (numeric)
Real (numeric)
Double (numeric)
Coordinate:
2D
3D
2D with angle
3D with angle
Date
Date and time
Time
Geological time
Angle
Boolean (logical)
Page 2031
Workspace Structure
Workspaces consist of one or more tables. In workspaces with more
than one table, these tables are related to one another. The
relationship is restricted to a one-to-many relationship in a simple
hierarchical or tree structure. The tree structure is limited to one
table (called the header table or primary table) that acts as the
trunk of the tree and subtables that act as the branches (called
secondary tables). This means that there is a single controlling
table, called a header table or key table, with many records in it.
Each record in this table is linked to many records in other tables:
Header table
Example:
Header table record owns 4
records in secondary table 1
Header table record also
owns 5 records in secondary
table 2
Secondary table 1
Secondary table 2
Exploration
Page 2032
Page 2033
Workspace Limits
There are very few restrictions on workspace size, provided you
organize your data in an effective manner and have adequate space
on your hard drive. For example, you can handle unlimited
numbers of geochemical sample points, drillholes, samples and
assays. Tables can be linked together to give data storage and
management capabilities for even the largest and most complex
exploration projects.
Data Types
Gemcom for Windows can accommodate the following data types in
workspace fields:
String
String fields are used to store any printable characters that can be
entered from the keyboard. This includes upper and lower case
letters, symbols, blank spaces and international characters. String
fields have a maximum length which you define when you first
create the workspace. It can range from 1 to 256 characters. Each
character requires 1 byte of storage space in the workspace. String
fields do not allow the entry of special values.
Memo
Memo fields are used to store bulk text of unlimited length. The
memo field can store the same type of data as the character field.
As well, it can store simple formatting characters such as tabs, line
feeds and carriage returns. Data can only be entered into memo
fields using the Workspace Editor (see Chapter 6: Editing Data), or
by using the Merge Bulk Text Data Into Memo function under
the Import or Merge Data command on the Workspace menu
(see Chapter 5: Importing and Merging Data). Each character
(including formatting characters) in the memo field of a record
Exploration
Page 2034
Integer
An integer is a number that does not have decimal places. Integers
can range in value from -2147483647 to +2147483647. Each integer
field requires 4 bytes of storage space in the workspace. Special
values can be entered into Integer fields.
Real
A real number is a low precision number that can have decimal
places. Real numbers are accurate up to six significant digits and
can have up to nine decimal places. If you enter numbers that have
more than six significant digits, you will lose precision on the least
significant of those digits (for example, 0.123456789 will be stored
as 0.12345, 123456789.0123456 will be stored as 123456000.000,
etc.). Each real field in the workspace requires 4 bytes of storage
space in the workspace. Special values can be entered into all Real
fields except DISTANCE fields in distance format tables, and FROM
fields in interval format tables.
Double
A double number is a high precision number that can have decimal
places. Double numbers are accurate up to twelve significant digits
and can have up to nine decimal paces. Each double number field in
the workspace requires 8 bytes of storage space in the workspace.
Special values can be entered into all Double fields except DISTANCE
fields in distance format tables, and FROM fields in interval format
tables.
Page 2035
Coordinate
Coordinate data types consist of either two or three double data
types linked together, representing the X, Y and, optionally, the Z
components of a right-handed orthogonal coordinate system.
Coordinate data types require either 16 or 24 bytes of storage space
in the workspace. There are two main coordinate data types:
Exploration
Page 2036
Date and time. There are four different date and time formats
available.
Date, Time and Date and Time fields do not allow the entry of
special values.
Geological Time
The fourth type of time data type is the geological time field. This is
a numeric field that you can use to record the relative age of a
deposit, for example, dating from a specific reference point in time.
Page 2037
Angle
An angle data type is a low precision number that can have decimal
places and represents angle measurements. Each angle field in the
workspace requires 4 bytes of storage space. Angles can be entered
as degrees (in one of four formats), as gradients, or as radians:
Boolean
Boolean fields contain single characters that represent either true
or false conditions. A Boolean field is displayed as a checkbox in the
Workspace Editor. Boolean true is entered by activating the
checkbox (); Boolean false by deactivating the checkbox (o).
Boolean fields require 1 byte of storage in the workspace and do not
allow the entry of special values.
Exploration
Page 2038
Not entered
Not sampled
Insufficient sample
Below detection limit
Above detection limit
Not calculated
Error
Not Entered
Not entered indicates that no data has been entered into a field.
In most cases it should be used as the default value when a
workspace structure is first defined so that when a new record is
created (either in the editors or in the import and merge
operations), the field has this special value.
The special value is entered as NE or as a blank field. The value is
shown on the screen and appears on reports or plots as entered.
Not entered values are not processed by all Gemcom for Windows
applications.
Not Sampled
Not sampled indicates that no sample has been taken, but a value
has been entered into the workspace.
Page 2039
Insufficient Sample
Insufficient sample indicates that a sample has been taken, but it
was insufficient to perform a reliable analysis.
The special value is entered as IS. The value is shown on the screen
and appears on reports or plots as entered.
Insufficient sample values are not processed by all Gemcom for
Windows applications.
Exploration
Page 2040
Not Calculated
Not calculated indicates that no value was calculated for this field
during one of Gemcom for Windows's data manipulation or data
analysis functions.
The special value can only be entered by the system during a data
manipulation operation. It is shown on the screen and appears on
reports or plots as NC.
Not calculated values are not processed by all Gemcom for
Windows applications.
Error
Error indicates that no value was calculated for this field during
one of Gemcom for Windowss data manipulation or data analysis
functions because an error occurred during the calculation. Typical
errors would occur as the result of an illegal mathematical
operation such as a divide by zero, or the log of a negative number.
The special value can only be entered by the system during a data
manipulation operation. It is shown on the screen and appears on
reports or plots as ERR.
Error values are not processed by all Gemcom for Windows
applications.
Types of Workspaces
Large volumes of data are collected during a typical exploration
project. Most of this data is located at known points identified by a
two- or three-dimensional coordinate, or by a distance or interval
along a line of known location and direction.
This type of data can be entered and managed very efficiently in
the four main workspace types: point, traverse, drillhole and
polygon.
Page 2041
Point Workspaces
A point workspace contains a single table which holds information
about points located in two- or three-dimensional space. Each
record in the workspace holds data for one point. Each field in the
record holds the location (2D or 3D coordinate) as well as
quantitative or qualitative data for that point.
Traverse Workspaces
A traverse workspace holds information that is collected along
straight lines in either two or three dimensions. Traverses are
defined by either a single coordinate at one end of the line, a
direction (an azimuth and optional dip angle) and a length, or by
coordinate values at each end of the traverse line. Information is
located along the line, either at points defined by distance
measurements along the drillhole, or in intervals defined by
starting and ending distances along the line.
Exploration
Page 2042
Page 2043
Drillhole Workspaces
A drillhole workspace holds information that is collected along lines
in three dimensions. Drillholes are defined by a single coordinate at
one end of the line and by directional data (for example, dip angles
and azimuths) measured at intervals along the line. Information is
located along the line, either at points defined by distance
measurements along the traverse line, or in intervals defined by
starting and ending distances along the line. Drillhole data is
always three-dimensional.
Polygon Workspaces
Polygon workspaces consist of coordinates that are collected
together to define the line segments which form closed polygons.
The workspaces can also include information about individual
polygons, entered and stored as polygon attributes. Polygons must
be associated with specific planes, and thus are two-dimensional;
however, the coordinates are expressed as three-dimensional
points.
Packet A
ORE
CU%: 1.01
Packet D
WASTE
CU%: 0.14
Packet B
ORE
CU%: 0.49
Packet D
ORE
CU%: 0.56
Page 2044
Selecting a Workspace
Before you can work with many of the commands available in
Gemcom for Windows, you must select a workspace. Use this
command to select a workspace from the active project.
1. Choose Workspace } Select Workspace. The Select Workspace
dialog box will appear.
2. Select the desired workspace from the list of available
workspaces and click OK.
Gemcom for Windows keeps track of the active workspace between
sessions as part of the session file; thus, the selected workspace will
stay active throughout the current session and any subsequent
sessions until another is selected.
Page 2045
Chapter 4
Introduction
Minimum Workspace Structures
The Workspace Structure Editor
The Menu Bar
The Toolbar
Creating a New Workspace
Modifying an Existing Workspace
Deleting a Workspace
Introduction
Before you enter any data into a Gemcom for Windows project you
must first create a workspace. You can change the structure of the
workspace any time after you have created and entered data into it.
Creating a workspace involves the following steps:
1. Selecting the workspace type. This depends on the type of
data that you want to enter and the format that you use to
collect the data.
2. Designing the workspace structure. This must be done
according to the way the data was collected and organized, as
well as the type of workspace selected. When you design the
workspace structure, be sure to include the minimum
workspace structure requirements for the type of workspace
that you have selected.
Exploration
Page 2046
Page 2047
Point Workspaces
The point workspace must have at least one table, a header table,
which must contain the following two fields as a minimum:
POINT-ID.
Exploration
Page 2048
Traverse Workspaces
Three different minimum workspace structures can be used for
traverse data. In each case, the minimum structure has at least one
table, the header table, which stores the information defining the
location and the orientation of the traverse line.
LOCATION.
LENGTH.
AZIMUTH.
TRAVERSE.
Page 2049
LENGTH.
AZIMUTH.
DIP.
TRAVERSE.
LOCATION-1.
LOCATION-2.
The rest of the data that you collect for the traverses can either be
placed in additional fields in the header table or stored in other
tables created in the workspace. Each of the other tables should be
in one of two formats.
One format can record points along the traverse, in which case the
table must have a field called DISTANCE with a real or double data
type. This will act as the secondary key for the table. The second
format can have data describing intervals along the traverse. In
this case, the table must have two fields, called FROM and TO
respectively, to record the distances from the collar to the start and
to the end of the interval. The fields can be either real or double
Exploration
Page 2050
data types. In this format, the FROM field will act as the secondary
key for the table.
If you plan to calculate composites, then you must define a field
called COMPOSITE in the header table and a field called COMP-ID in a
composite subtable. Both must be string data types with lengths
12 and 10, respectively.
Drillhole Workspaces
Three different minimum workspace structures can be used for
drillhole data, each with a minimum of two tables. The minimum
structure defines the location and orientation of the drillhole. This
information is split between the Header table and the Survey table.
In all three cases, the minimum requirements for the header table
are the same. The header table must contain information about the
starting location (or collar) of the drillhole. This data is defined by
three fields:
HOLE-ID.
LOCATION.
LENGTH.
If you have interval or distance type survey data, you may also
want to include the following field in the header table:
TRACE-TYPE.
Page 2051
HOLE-ID.
TO.
AZIMUTH.
DIP.
HOLE-ID.
DISTANCE.
AZIMUTH.
DIP.
Exploration
Page 2052
HOLE-ID.
LOCATION.
PCX_SEQ_NO.
When you create a drillhole survey table based on the point survey
type, the Workspace Wizard will also add the following two fields:
AZIMUTH.
DIP.
Page 2053
data types. In this format, the FROM field will act as the secondary
key for the table.
You can also have tables in a drillhole workspace that do not
comply with these minimum structures, but you will not be able to
use them for any of the normal Gemcom for Windows processes.
If you plan to calculate composites, then you must define a field
called COMPOSITE in the header table and a field called COMP-ID in
the composite table. Both must be string data types with lengths
12 and 10, respectively.
Polygon Workspace
There are three different workspace structures for polygon
workspaces. The structure used depends on how you are planning
to use the workspace. Polygon workspaces which will be used for
geological modelling and ore control operations require a minimum
of three tables, while polygon workspaces used for other purposes
require only two tables as a minimum. Most of the commands on
the Polygon menu work best with polygon workspaces of either a
geological modelling or ore-control subtype.
POLYGON.
Exploration
Page 2054
PLANE.
OUTLINE.
POLYGON.
LOCATION.
PCX_SEQ_NO.
POLYGON.
ROCKCODE.
GRADE1.
GRADE2.
THICKNESS.
Page 2055
DENSITY.
AREA. This field, which must be a double data type, will contain
the total area of the polygon.
VOLUME.
DATE.
POLYGON.
Exploration
Page 2056
CLOSED.
POLYGON.
LOCATION.
PCX_SEQ_NO.
User-Defined Workspaces
User-defined workspaces have the least stringent minimum
requirements of all the workspace types. A user-defined workspace
must have at least one table, a header table, which must contain
the following fields as a minimum:
PCX_SEQ_NO.
Page 2057
ID. This field, which must be a string data type, is the primary
key and thus will contain an identifier for each record.. Unlike
the primary key fields for the other workspace types, it does not
have to be unique, because of the unique PCX_SEQ_NO field. If
you do not make the primary key field unique, however, you
may experience problems when editing workspace data. If you
modify or delete a given record, the data in any other record
with identical ID data will also be modified, even though the
PCX_SEQ_NO field will be different.
Title bar
Menu bar
Toolbar
Workspace modification pane
Table modification pane
Field modification pane
Status bar
Exploration
Page 2058
Title bar
Menu bar
Toolbar
Workspace
modification
pane
Table
modification
pane
Field
modification
pane
Status bar
Title Bar
The title bar displays the name of the program (Structure Editor).
It also contains the minimize, restore (or maximize) and close
buttons.
Page 2059
Status Bar
The status bar displays the current status of the Structure Editor.
If one of the toolbar buttons or menu commands is selected, or if the
mouse cursor is placed on one of the toolbar buttons, the function of
that button or command will be displayed in the status bar.
Exploration
Page 2060
Workspace
The Workspace Menu contains five commands for creating,
modifying and saving workspace structures.
New
This command allows you to create a new workspace. For more
information on creating workspaces, see page 2064.
Page 2061
Open
This command allows you to open an existing workspace structure
so you can modify or view it. For more information on modifying
workspaces, see page 2071.
Save
Use this command to name and save a new workspace or to save
changes to an existing workspace.
Save As
Use this command to copy or rename an existing workspace by
saving it to another name. Note that this command copies both the
workspace structure and any data stored in the workspace and
saves them to the new name.
Exit
This command closes the Structure Editor and returns you to the
Gemcom for Windows graphical work area.
Edit
This menu has three commands.
Undo
This command allows you to undo your last edit.
Exploration
Page 2062
Delete
This command deletes the highlighted text without deleting the
row.
Delete Rows
This command deletes the highlighted row, including any text.
Insert
This menu has one command.
Rows
Selecting this command will insert a row above the row in which
the cursor is currently located.
View
This menu has four commands.
Toolbar
This command allows you to toggle the display of the toolbar on and
off. By default, the toolbar is toggled on, and you will see a
checkmark to the left of the command. If you do not wish to see the
toolbar in the Structure Editor, clicking this command will toggle
the display off.
Status Bar
This command allows you to toggle the display of the status bar on
and off. By default, the status bar is toggled on, and you will see a
Section II: Workspaces
Page 2063
checkmark to the left of the command. If you do not wish to see the
status bar in the Structure Editor, clicking this command will
toggle the display off.
Next Pane
Selecting this command will move the cursor to the next window
within the Structure Editor. For example, if the cursor is currently
located in the workspace modification pane, selecting Next Pane
will move the cursor to the table modification pane.
Previous Pane
Selecting this command will move the cursor to the previous
window within the Structure Editor. For example, if the cursor is
currently located in the field modification pane, selecting Previous
Pane will move the cursor to the table modification pane.
Help
This menu has three commands.
Contents
This command allows you to access the main contents window of
the structure editor online help.
Search
This command allows you to search for a specific topic in the
structure editor online help index.
Exploration
Page 2064
About strucedit
This command displays program information about the structure
editor.
The Toolbar
The Structure Editor toolbar has six buttons:
Button
Name
New
WorkspaceNew
Open
WorkspaceOpen
Save
WorkspaceSave
Insert Rows
InsertRows
Delete Row
EditDelete Rows
About
AboutAbout strucedit
Page 2065
Click Next.
Exploration
Page 2066
Drillhole workspace
Point workspace
Polygon workspace
Traverse workspace
Other (user-defined)
Geological Modelling
Ore Control Operations
Other
Click Next.
2. Enter the following parameters:
Primary Key. Enter the name of the field from the header
table that will be used as the primary key field for all the
tables in the workspace. The suggested default name for the
type of workspace you are creating is already entered for
you.
Page 2067
Click Next.
Exploration
Page 2068
Page 2069
Page 2070
From Template
If you have pre-existing workspace templates from older Gemcom
DOS applications, or if your organization has created workspace
templates of its own, you can create new Gemcom for Windows
workspaces based on these templates.
Page 2071
Workspace Level
At the workspace level, you can modify a workspace by adding a
new table or deleting an existing table.
Adding a Table
Follow this procedure to add a new table to the selected workspace:
Exploration
Page 2072
1. Click the cell in the last row and column of the workspace
modification pane and press [Enter] or [Tab] to add a new row
to the grid.
2. Enter the following parameters for the table you wish to create:
Table Name. Enter a name for the table. You can enter
your own name, or you can select from among the default
names in the list provided. The table names available on the
list will depend on the type of workspace you are modifying.
Table Type. Select one of the types listed. The table types
available will depend on the type of workspace being
modified.
3. The key field will have automatically been added to the table
modification pane. If you selected either the Point or User table
type, a PCX_SEQ_NO field will also have been added to facilitate
record sorting. To define additional fields for the table, see
Table Level on page 2073.
Deleting a Table
If you delete a table, all associated fields, along with any data
entered into them, will also be deleted. Once you have deleted a
table and saved the workspace structure, you will not be able to
recover this data.
To delete a table, follow this procedure:
1. In the workspace modification pane, select the table that
you wish to delete by clicking the button to the left of the table
name in the grid. The row will be highlighted, and a triangular
arrow will appear in the selection button.
Page 2073
Click on one of
these buttons to
select a table
2. Select Edit } Delete Rows (or click the Delete Rows button).
Table Level
At the table level, you can modify a table by adding a new field or
deleting an existing field.
Adding a Field
Follow this procedure to add a new field to a table in the selected
workspace:
1. In the workspace modification pane, select the table to
which you wish to add a field by clicking the button to the left of
the table name in the grid.
The row will be highlighted, and a triangular arrow will appear
in the selection button.
2. Click in the cell in the last row and column in the table
modification pane and press [Enter] or [Tab] to add a new row
to the grid.
3. Enter the following parameters for the field you wish to create:
Exploration
Page 2074
Field Name. Enter a name for the new field. For many
Gemcom for Windows functions, specific field names must
be assigned in specific tables. See Minimum Workspace
Structures on page 2046 for details. You can enter your
own name or select a name from the default names on the
list provided. The names available will depend both on the
type of workspace and the type of table you are modifying.
Field Type. Select the type of field you wish to create from
the pick. For more details on each type of field, see Data
Types on page 2033.
Deleting a Field
1. In the table modification pane, select the field that you wish
to delete by clicking the button to the left of the field name.
The row will be highlighted, and a triangular arrow will appear
in the selection button.
2. Choose Edit } Delete Rows (or click Delete Rows).
If you delete a field, any data that has been entered into the field
will also be deleted. Once you have deleted a field and saved the
workspace structure, you will not be able to recover this data.
Field Level
To modify a workspace at the field level, you can edit the properties
of a selected field.
Page 2075
Exploration
Page 2076
Memo Fields
If the field is a memo field, no property parameters will appear. A
memo field is a special type of string field that can store unlimited
amounts of bulk text, including simple text formatting characters.
Boolean (Logical) Fields
If you selected Boolean as your field type, the following parameter
will appear:
Time Fields
If you selected Time for the field type, enter following parameter:
Page 2077
Date Fields
If you selected Date as the field type, the following parameters will
appear:
Exploration
Page 2078
information on system date format, see your Windows documentation or online help.
Page 2079
Angle Fields
If you selected Angle as the field type, the following property
parameters will appear:
Exploration
Page 2080
Coordinate Fields
If you selected 2D Coordinate, 3D Coordinate, 2D Coordinate
with Angle or 3D Coordinate with Angle as the field type, enter
the following parameters for each axis (X and Y for 2D coordinates;
X, Y and Z for 3D coordinates):
Page 2081
Deleting a Workspace
You can delete an entire workspace from your active Gemcom for
Windows project.
Use this command with extreme caution! If you delete a workspace,
all associated tables and fields, along with any data entered into
them, will be lost. You will not be able to undelete this workspace!
If you are sure you want to delete this workspace, click Yes.
Exploration