![]() |
|
![]() |
||||
|
| Problem: | The Tour went away |
| Symptom - The
Tour screen does not appear when the program starts. |
|
| Cause - The tour was closed with the End Tour button. | |
| Solution - Open the Database Window with F11. Click on the Forms tab, then double-click on the Tour form. If you want to close the tour but have it come back next time, use the close button instead of the End Tour button. |
| Problem: | How do I get started with importing? |
| Solution -
First, walk through the tutorial in this documentation, or on-screen using
the Tour. Refer to the Getting Started booklet for instructions on
creating your new database. Select a simplified set of your data, and
format it into Data Transfer Standard format using the Excel file provided
with your software. Import it into a test database, then use TreeView and
other output options to view the data. Add more complex data, like sample
QC information or multiple analyses. Again view the data and how it is
stored in Enviro Data. |
| Problem: | F11 doesn't bring up the database window |
| Symptom - Can't bring up database
window with F11 function key. |
|
| Cause - Possibly changed when computer was set up for overhead video presentation. | |
| Workaround
- Select Window from the Access
toolbar. Select Unhide. Select EnvDProg: Database window. |
| Problem: | Subset doesn’t work |
| Symptom - Trying
to create a subset brings up an error message “Verify that the path to
the BlankDB.mdb file...... ” |
|
| Cause - The program database directory must contain a copy of an Access database file called BlankDB.mdb. | |
| Solution - Locate a copy of the file (or obtain it from Geotech ) and place it in the proper folder. |
| Problem: | Site Name Error during import |
| Symptom - Site Name Error is displayed
at the start of an Excel import. |
|
| Cause - Blank lines at the end of the Excel file | |
| Solution - Delete
Blank lines. It may be necessary to copy and paste the data into a new
Excel file. |
| Problem: | What should I do with historical data where I have
very little information besides the station, date, value and "less
than" sign? |
| Solution - The
simplified data transfer standard format would probably be the best place
to start for this type of data. You can even hide the columns that you
have no data for, and just populate the required fields. |
| Problem: | Import does not go to completion |
| Symptom - The import appears to
“hang” with large numbers of records |
|
| Cause - The import wizard is performing data transfer and checking tasks that can take some time. Import speed is related to network and computer resources, however, Geotech has found that most clients can import up to 10,000 records within 30 minutes to an hour. The import speed increases exponentially above that number of records. | |
| Solution - - We
highly recommend that you import in record batches of 10,000 or less. If
you are splitting a large data file, take care to sort it by station, then
split the file between stations. Otherwise your duplicates and supersededs
may be incorrectly set. |
| Problem: | Problems with Access References "Automation Error". | ||||
| Symptom - Doing something,
usually in a form, results in a message that includes the text
"Automation Error". |
|||||
| Cause - References
in the References Collection do not agree with the versions of the .dlls,
.ocxs and other objects on the user's computer. |
|||||
Solution - Make Access
rebuild
the References Collection. Do this by:
|
| Problem: | The graph went away | |||
| Symptom - Graphs on the graph form and graph reports don’t appear.
Graphs in other Access applications also will not appear. |
||||
| Cause - - The Graph9.exe program, part of Microsoft Office, has become corrupted. | ||||
Solution - Replace the file by:
|
| Problem: | Problems with Access References | ||
| Symptom - Doing something, usually in
a form, results in a message like “There is no object in this
control.” or “Object does not support this property or method.” |
|||
| Cause - An .ocx, usually Comdlg32.ocx is not present or not properly registered. | |||
Solution - To
register the .OCX. do this:
|
| Problem: | Installable ISAM Error |
| Symptom - All
seems to be working as it should until I attempt to import a file. I get
the error "Couldn't find installable ISAM". |
|
| Cause - Missing file filter extension for Access. | |
| Solution - Re-run MS
Office 97 setup and add the text file filter under Data Access
. If this does not fix it,
follow the procedure in the link below. |
| Resources - ACC: Troubleshoot "Couldn't Find Installable ISAM" Error | |
| Problem: | Double Quotes in Parameters with commas |
| Symptom - When using Excel to edit
ASCII text files, it places double quotes when there are commas. |
|
| Cause - When saving an Excel file as a tab delimited file, there is a conflict when any cell contains a comma. Excel places double quotes around the item in that cell. | |
| Solution - Because parameter names often contain commas, this happens frequently when editing files in Excel. The workaround is a macro that is kept in a spreadsheet template. To use this macro, just copy the attached file into the directory C:\ProgramFiles\Microsoft Office\Templates\Spreadsheet Solutions. |
| Resources
- TextExport.xlt
|
|
| Problem: | Can't find library on Program open |
| Symptom - Copied new queries, tables
and reports into EnvDProg. Code error on program open. |
|
| Cause - Geotech
is
using a newer version of the comdlg32.ocx file than the user. When the new
files are copied |
|
| Solution - Close
the program after stopping the code. Reopen the program. Select a module,
open in design mode. Then select Tools - References. If there is an error
"MISSING - Microsoft Common Dialogue Control", then uncheck that
box. Browse the Windows
\System subdirectory, select
comdlg32.ocx. This re-registers the older version of the Microsoft Common
Dialogue Control. Close the program and reopen it. It should open without
problems. |
| Problem: | Valid Access functions don't work | ||||
| Symptom - Displays
the error "Function is not available in expressions in query
expression …" when the program is opened. |
|||||
| Cause - References
in the References Collection do not agree with the versions of the .dlls,
.ocxs and other objects on the user's computer. |
|||||
Solution - Make Access
rebuild
the References Collection. Do this by:
|
| Problem: | ODBC Connection failed |
| Symptom - Attempting to connect to SQL
Server
, get error message that connection failed.
Subsequent testing yielded timeout errors. |
|
| Cause - Stopped SQLExecutive service. | |
| Solution - Reloaded
SQL driver from the Office CD. Deleted and recreated the ODBC
data source. However, this didn't solve the timeout problem.
Restarted the SQLExecutive service, and logon went through. NOTE: This
problem was computer specific, no one could log on from this computer,
however, others could log on from different computers with SQLExecutive
stopped. |
| Problem: | Compile error: Can’t find project or library |
| Symptom - Installed
EnviroData from install program furnished on CD by Geotech
. Can't get past program
loading main menu. |
|
| Cause - - Install
did not correctly register the OCX's during install. Likely problem was
the program looking for the Blue Marble OCX, which should have been
unchecked before the program was included in the install. |
|
| Solution - Open Access , and select EnvDProg.mdb from the file menu. If it's not on the list, open EnvDProg, close out of the error dialogue box and the program, and it should then be on the file list. This action will open the program without executing the autoexec macro. Press F11 to bring up the database window, and select the Module tab. Then select any module, and click on the "Design" button. Move to the main Access menu at the top of the screen and select "Tools - References". There will be a list of checked references; these should include Microsoft Windows Common Controls, Microsoft DAO 2.5/3.5 Compatibility Library, Microsoft Common Dialog Control, and others. One or more of the listed checked references will probably say "MISSING". If it is Blue Marble GeoObjects Map Control, uncheck that box and click OK. Close the program and reopen from the icon; it should open normally. If it is the Common Controls, or the Common Dialog Control, uncheck the box and click OK. Then re-open Tools - References and select Browse, move to the Windows\System subdirectory. The install program should have copied the comdlg32.ocx and comctl32.ocx files to that subdirectory. Select the appropriate OCX, click on OK, close the program and restart. |
| Problem: | Unable to register comcat.dll |
| Symptom - Error
on install states that comcat.dll did not register, and the program
install did not complete successfully. |
|
| Cause - Comcat.dll version in install is unable to overwrite version currently installed on the computer. | |
| Solution - - Try
opening the program anyway. In Windows operating systems, the install has
often completed successfully. If program
opens with an error, it likely means that
one of the program OCX's did not register correctly. See error message on
registering OCX's. |
| Problem: | TreeView control doesn't display data |
| Symptom - The TreeView form opens
properly, and displays a white background but no data. In design view the
control is present but not visible. |
|
| Cause - There is a problem with the registry entries for the OCX. | |
| Solution - Close the database. Assuming the OCX is in the Windows \System folder, enter the following command under Start, Run: regsvr32.exe "c:\windows\system\comctl32.ocx". Then re-open the database. |
| Problem: | Enviro Data not printing Base Map |
| Symptom - Only well locations, values,
and station names, if selected, print direct from Enviro Data |
|
| Cause - Blue Marble (provider of the map module) does not support printing the base map file in release 2.1. | |
| Solution - Geotech
will incorporate version 2.5 of Blue Marble's GeoObject
control, which reportedly does support base map printing. |
| Problem: | Excel stations import error |
| Symptom - Excel stations import error
generates "Unexpected error from external database driver"
error. |
|
| Cause - Problem
with Excel file. |
|
| Solution - Copied data from client Excel file (data only, not header) into Station Import file provided with the software. Program proceeded normally with that file. |
| Problem: | Cannot create a reference file |
| Symptom - Error message says it cannot
locate the temp.mdb file |
|
| Cause - The Blank setting in the Control table is pointing to the incorrect location. | |
| Solution - Modify
the Blank setting in the Control table to point to the BlankDB.mdb file
that was installed on the client machine. Through the user interface: From
the Enviro Data Main Menu form, click on Admin. Then click on Edit
Settings. Correct the Control Text field for the Blank Control. Then try
to create the reference file. |
| Problem: | Reference not on list |
| Symptom - Tried
to re-install the references, but Microsoft DAO 2.5/3.51 Compatibility
Library was not on the list. |
|
| Cause - Access may need to be re-installed. | |
| Solution - From
the references window click on browse. Browse for C:\ProgramFiles\CommonFiles\Microsoft
Shared\DAO\dao2535.tlb and click on OK. If this directory is not complete,
Access
needs to be re-installed. |
| Problem: | |
| Symptom - |
|
| Cause - Microsoft Access XP changed the way linked tables associate with an Access program file which causes severe delays on some machines. | |
|
Solution - Depending on your work environment, there are several solutions for this problem: 1) If your environment utilizes only one project (data) database, simply wait for Access to fully reference the project database, and continue working as normal when the "Select Data" form does appear. The wait time for Access XP to create these references is approximately 15-20 minutes if the project database resides locally on your machine, or 20 - 30 minutes if the project database resides on a network server. Once the reference is fully established, you will no longer have to wait for your "Select Data" form to appear unless you attach to another project database, even when you close and re-open Enviro Data. 2) If your environment utilizes more than one project (data) database, solution #1 will most likely not work for you. We suggest reverting your machine back to Access 2000, or upgrading to Access 2003, which will solve this performance problem. |
| Problem: | |
| Symptom -
|
|
| Cause - The drawing file may be in the wrong format, or may contain invalid objects, or both. | |
|
Solution - First open the drawing that you wish to use in AutoCAD. Next open the Radind.dwg file that comes with Enviro Data. In Radind.dwg, select all objects and delete them. In your drawing, select all objects and copy them to the clipboard. In Radind.dwg, paste using original coordinates (an option on the Edit menu). Use Save As on the File menu to save the file to a new name, in Release 14 format. Close out of ACAD, and you should be able to enter your file in the Sites table and create your map. If you decide to edit the map, be sure when you save it to use Save As and specify the Release 14 format. |
|
| Problem: | OCXs won’t register in Windows XP |
| Symptom
- When you try to install Enviro Data in Windows
XP, you get messages that OCX files didn’t regieter. |
|
| Cause - Administrator privileges are required. |
| Solution
- Uninstall Enviro Data using the Setup program. Log off your user
account, then log in using an account with administrator privileges.
Re-install Enviro Data. Then you can log off the administrator account,
and log backing as a user. |
|
| Problem: | Access 2003 is displaying multiple security messages |
| Symptom - When you open Enviro Data (or other Access applications) Access gives several warnings about potentially dangerous code, which you need to click through every time. | |
| Cause -Microsoft changed the security model in
Access. |
|
| Solution
- You can return your Access to the security level of previous versions.
On the Access menu bar, click on Tools/Macro/Security. Set the Security
Level to Low. Say “No” to “Block Unsafe Expressions” if asked. On
some computers you may need to do this twice to get it to take effect. |
|