|
RTLA Frequently Asked
Questions
- Database Questions
- Wrong date entered for a plot.
Changed the date in the handheld file and reloaded data.
Need to delete old data. Commands do not seem to run.
- Needs to change the date of
data already loaded from handheld data.
- Changing plots numbers
- SQLBase for Windows installations
- Introduction to the LCTA database
- LCTA Program Manager fact sheet
- Handheld Data Loggers Questions
- Handheld program does not
read the species file.
- Handheld computer CMT MC-V
will not hold charge.
- When editing handheld files
using the handheld program edits are not saved.
- When entering C for prescribe
burn (< than 1 yr) in handheld program data is not
loaded in the database using the LCTA program.
- Cannot load handheld data
file - getting the message "cannot add unique value
to table".
- How can I get rid of extra
rows typed into the belt portion of the HH program?
- Problem loading handheld files.
- Handheld files are not loaded
into the database.
- Handheld data screens.
- Loading and unloading files
using kermit for the CMT MC-V.
- Corvallis Micortechnology
handheld computer configuration reference.
- Data Recording Using The
Micro Palm PC/4000 And Corvallis Microtechnology MC-V
Handheld Computers For The Land Condition Trend Analysis
Program.
- Programmer's File Editor
(text editor program)
- LCTA Program Manager Questions
- The Calculate K program
in the LCTA Program Manager does not work.
- Calculated K values are
very low or negative.
- GPF error when using view/enter/edit
option of the data menu in the LCTA Program Manager.
- Error PC010 Invalid Plotid
when running PCC. May occur in other analyses.
- Unable to correct errors
listed in error file from LandUse Analysis.
- Erosion analysis in LCTA
Program Manager is generating message "slope values
missing from soills".
- Cannot see entire text result
file from tactical concealment program. It is getting
cut off after a certain number of plots are described.
This may occur with other output files from the LCTA
Program Manager analyses.
- Getting GPF when using Upload
handheld files option from LCTA PM.
- LCTA Users Interface quick
reference.
- LCTA database table interactions.
- Quest Questions
- Unable to open entire Aercover
table in order to edit data.
- Trying to export data from
Quest 1.2.3 to a Dbase file - gets a stack overflow when
reaching 32,000 rows.
- How do I count the number of
distinct variable in a query and how do I use excel to
achieve similar results.
- Quest does not working after
relocating the program to another drive without re-installing.
- Loaded Quest, SQLBase for Windows
and LCTA Program Manager. Now I get the message "Failure
on connect can not find DBWINDOWS" from Quest. Cannot
connect to database from the LCTA Program Manager.
- When trying to open large tables,
messages appear "Database access error, cannot read
or write to database".
- No SQL button in the toolbar
of Quest version 1.2.3.
- Could not get a list of databases
in Quest.
- How do you look at and edit
long varchar data (plotnote in the Plotsurv table)?
- How do I print a Long Var
Char field?
It seems that version of 1.2.3 of Quest only likes dates in the
format 7-3-1996 (not 7/3/1996) in delete statements.
Back to Top
Add a line to plotsurv with the plot and new date. Run a series
of SQL statements to change data in all data tables to the correct
date. Delete line in plotsurv with incorrect date.
Back to Top
Insert the new plot number in plotmast and plotsurv. Run SQL to
change all dependent data then delete original plot number from
PLOTSURV.
Back to Top
The following file is a Rich Text Format (RTF) file. After it
has been downloaded use a word processor program that supports
the RTF format to view the file.
[D4.rtf] (6K)
Back to Top
The following file is a Rich Text Format (RTF) file. After it
has been downloaded use a word processor program that supports
the RTF format to view the file.
[D5.rtf] (11K)
Back to Top
The following file is a Rich Text Format (RTF) file. After it
has been downloaded use a word processor program that supports
the RTF format to view the file.
[D6.rtf] (1200K)
Back to Top
In most cases the species file should have the first three letters
of the installation name with an extension of spp, for example,
Fort Bennings species file is named ben.spp. This file should be
located in the root directory of the handheld computer.
Back to Top
Batteries need to be replaced.
Back to Top
There is a bug in the handheld programs. After editing a handheld
file and saving changes, exit the program, then re-start it to
make sure the edits have been applied.
Back to Top
Desktop program will not load this data if C or P is entered -
only X is accepted (THIS IS A BUG).
Back to Top
The plot had been measured in previous years and the handheld
data file was marked as an initial inventory file not a long-term
monitoring. Open the data file in notepad and replace the line
INVENTORYI with INVENTORYL.
Back to Top
Use the space bar to delete the vegid for each row you want to
get rid of. Rows without a vegid will be ignored during the Upload
Handheld Files process.
Back to Top
Handheld data files must be copied on to the PC in the hhfiles
directory, not in subdirectories under hhfiles.
Back to Top
Check the instalid on line 3 of each handheld data file. This
code should match the three letters following LCTA in the name
of the database. For example, Fort Hood's database is named LCTAHOO
- the instalid on line 3 of the data file should read HOO. Also,
the handheld file name must begin with the first two letters of
the instalid. In the example above all valid handheld file names
will begin with HO.
Back to Top
The following file is a Rich Text Format (RTF) file. After it
has been downloaded use a word processor program that supports
the RTF format to view the file.
[HH9.rtf] (25K)
Back to Top
The following file is a Rich Text Format (RTF) file. After it
has been downloaded use a word processor program that supports
the RTF format to view the file.
[HH10.rtf] (2K)
Back to Top
The following file is a Rich Text Format (RTF) file. After it
has been downloaded use a word processor program that supports
the RTF format to view the file.
[HH11.rtf] (18K)
Back to Top
The following file is a Rich Text Format (RTF) file. After it
has been downloaded use a word processor program that supports
the RTF format to view the file.
[HH12.rtf] (78K)
Back to Top
This program is a very useful text editor that can open multiple
files in their own windows. Very useful for looking at your handheld
data files. This program is freeware.
Links are provided below for general information about the program
(HH13.rtf), copies of the program for various systems, and a link
to the PFE home page.
The following file is a Rich Text Format (RTF) file. After it
has been downloaded use a word processor program that supports
the RTF format to view the file.
[HH13.rtf] (11K)
PFE for Windows 95, Windows NT 3.51 Intel, and Windows NT 4.0
Intel
[pfe0602i.zip] (452K)
PFE for Windows NT 3.51 PowerPC and Windows NT 4.0 PowerPC
[pfe0602p.zip] (508K)
PFE for Windows 3.1x
[pfe0602.zip] (438K)
Back to Top
Try using a newer version of the LCTAKVAL.EXE program.
Back to Top
Some CalcK values appear to be negative or very small due to high
organic matter percent in soil samples. Soilsample collection may
have been done incorrectly(included O-horizon).
Back to Top
This is a known error on some systems. Do not use this option.
Back to Top
Plottype for the plot was marked as SPUSE in plotsurv. Change
to S for all plots, also change CORE to C.
Back to Top
Analysis did not recognize "Ax Burn > 1yr" in maintain
field of Maintact. This code was put out by the handheld program
but is unacceptable to the LCTA Program Manager. Change all to "Ac
Burn > 1yr", then re-run analysis.
Back to Top
Values are present from initial inventory year but rows are present
for subsequent years in soills but slope and slope length cells
are null. This appears to be related to a glitch with the handheld
program. Use statement "delete * from soills where slope is
null and slplen is null;" to get rid of offending lines.
Back to Top
Open TACTCONA table in quest to see the entire result set, or
open .txt file in notepad or word processor. This error is caused
by the limits of the file viewer in the LCTA Program Manager.
Back to Top
No handheld files were in the /LCTA/PRGMS/HHFILES directory.
Back to Top
The following file is a Rich Text Format (RTF) file. After it
has been downloaded use a word processor program that supports
the RTF format to view the file.
[LCTA9.rtf] (16K)
Back to Top
The following file is a Rich Text Format (RTF) file. After it
has been downloaded use a word processor program that supports
the RTF format to view the file.
[LCTA10.rtf] (7K)
Back to Top
Table is too large. Best to use menu-driven queries or SQL statements
to see the portions of the data you are interested in. This will
save you time and allow you to make universal changes as well.
Back to Top
Export the data in parts. It seems that in version 1.2.3 of Quest
there is a bug when using the Copy To option of the Edit menu item.
I think the error is caused by the program displaying the number
of rows copied in the lower left corner. Once the number reached
32,000+ rows the program fails. It seems that the variable in the
program holding the number of rows is an integer which has a limit
of about 32,000.
Back to Top
Use the count function in QUEST or use a pivot table if data is
in excel.
Back to Top
Re-install Quest using the Setup program provide on the Quest
disk.
Back to Top
The version of the LCTA Program Manager installation program from
CERL renamed SQLAPIW.DLL to SQLAPIW.XXX. Since the original SQLAPIW.DLL
was the correct file - delete SQLAPIW.DLL and rename SQLAPIW.XXX
to SQLAPIW.DLL. LCTA Program Manager could not connect to the database
because of the same problem.
Back to Top
Error message caused by full hard drive. Hard disk space must
be freed up for tables to be opened.
Back to Top
Add the line Activity5=SQL.DLL (or next activity number) to the
quest.ini in the /gupta directory.
Back to Top
Try starting the database engine (DBWindows) manually before starting
Quest. There should be an icon in the Gupta Windows group for the
database engine.
Back to Top
In Quest, long varchar fields ( or memo fields) appear as a gas
gauge with E and F. The read line between the E and F indicate
data is present. Double click on the gas gauge to open a viewing
window.
Back to Top
Cut and paste the info into another application or use the Quest
report builder to create a report.
Back to Top
|