GIS Layer Transfer Wizard
- Install problem: Not registering OLEAUT32.DLL during installation.
- General Troubleshooting: Not able to complete a Shapefile import to Hydra using the “Layer Wizard”.
- Run Time Error 2: Overflow
- Run Time Error 5: Invalid procedure call or argument
- Run Time Error 9: Subscript out of range
- Run Time Error 13: Type mismatch
- Run Time Error 63: Bad record number
- Run Time Error 380: Invalid property value
- Run Time Error 3015: [field] isn’t an index in this table.
- Run Time Error 3021: No current record
- Run Time Error 3075: Syntax error missing operator in query expression
- Run Time Error 3131: Problem with ‘from’ clause
- Run Time Error 3256: Index file not found
- Run Time Error 3285: Invalid index definition
- Run Time Error 6128: Invalid procedure
- Run Time Error 3163: Field too small to accept the amount of data you attempted to add
- Run Time Error 3265: Item not found in this collection
- How do I import from AutoCAD Map with ID#’s in object data?
- How can I add pipes using ArcView to an existing Hydra model without changing my G_ID#’s?
- “[filename]” isn’t an index in this table. Look in the indexes collection of the TableDef object to determine the valid index names.
- Data type conversion error
- No viewable fields
- Expected “nod,str” but found “END” at line ___ in path “….DXA”. Layer export failed.
During installation, if your OLEAUT32.DLL is older than the version being installed for the GIS Layer Transfer Wizard, the install program will instruct you to re-boot your computer before trying the install program again. However, as this is a critical file, some
versions of Windows will not update this DLL on reboot. The solution is to first install the latest service pack for Windows from
Microsoft, and then install GIS Layer Transfer Wizard.
The Microsoft Access MDB database, called PROJECT.MDB, which stores Hydra’s analysis results has reached it’s maximum file size, and cannot hold any additional analysis run results. If your project is very large, or if you have stored a large number of analysis runs, you will need to do one of the following:
- Delete extraneous analysis runs from your results database and “pack” the database to completely remove the records. You can use the database packing function in Hydra’s File menu.
- Create a subfolder in your Project Directory for the PROJECT.MDB which includes your previously stored analysis runs. Then Hydra will automatically create a new empty PROJECT.MDB file for future analysis runs. Especially if you project is very large, you might consider using a separate PROJECT.MDB file kept in a separate subfolder for each analysis scenario.
There are many possible causes of problems doing a data transfer. Here are some tips to avoid some of the most common problems:
File Naming Problems: Check to make sure your Shapefile names are 8 characters or less, and do not contain hyphens “-“, and that the SHP and DBF files have identical names. Make sure the path to your Shapefile is no longer than 255 characters.
ID# must be unique — If your identification numbers (ID’s) are not unique, you will get the error “duplicate key field values found in source table”. Make sure your identification field in the DBF contains a unique numeric value for each record. In the case of a collection system layer, there must not be duplicate values between the nodes and links — you cannot have Nodes numbered 1 to 1000 and Links numbered 1 to 1000. If you have this problem, you can use an update query in Microsoft Access to change the numbering system before you do the import with Layer Wizard.
Consistent field type — ID fields may be numeric or character, but for a collection system layer, they must both be the same — you cannot have a Node ID field that is character, and a Link ID field that is numeric. Also, make sure your source table fields are not larger than 32 characters wide. You can put numeric data into a character field, but you cannot put character data into a numeric field.
File Format Problems: Make sure your Shapefiles are valid. If you have created them from another application other than ArcView, you may encounter problems. Check to be sure the DBF files created are dBASE III files. You should be able to open the DBF file in any application and see the data.
Field Size Problems: If the fields your are mapping from your source table are larger than the field widths in Hydra’s DBF, you may need to adjust the field widths. You can use two instances of the WCREATE tool to compare the structure of the source and target tables side-by-side.
The DBF tools, WBrowse and WCreate are excellent “free ware” tools for reviewing and modifying your DBF data and file structure.
Back to Top
Early versions of the GIS Layer Transfer Wizard may display these errors when exporting from Hydra parcel layer to a shapefile, or when a layer contains more than 32,000 entities. This problem is fixed in Nov 5, 2004 Transferwizard.EXE and HydraGIS.DLL program files and later.
This is likely caused by a problem with a program file. Uninstall the Layer Transfer Wizard program, reboot, then reinstall. If the problem continues doesn’t work, consider reinstalling your operating system.
NOTE: Check to make sure you only have the Layer Transfer Wizard installed once on your computer. Do a search for TransferWizard.EXE on your computer. If it is installed more than once, uninstall them all, reboot your computer, then reinstall using the latest installation program from CD (October 2000).
ALSO: The AutoCAD 2000i (or later) installation sets the default for file type .SHP as an AutoCAD Shape Source. Consequently, Layer Transfer Wizard seems to have a problem recognizing .SHP files after installation of AutoCAD. Also, when the file types are hidden, Layer Transfer Wizard can’t find the .SHP files. In Windows File Explorer, in the Tools menu, select Folder Options. On the View tab, uncheck ” Hide file extensions for known file types”.
If the problem continues, call Pizer Technical Support at 206-634-2808
Back to Top
GIS Layer Transfer Wizard gives “RTE 9 Subscript out of Range” on import of a Shapefile to a Hydra PA_ parcel layer.
Type Mismatch: For combining the node and link tables into an SY layer, make sure both ID fields used are the same type, either character or numeric.
Invalid Index Definition: Be sure your source ID field(s) are 32 characters or less, to match the target field(s). For SY layers, make sure your node ID and link ID fields are the same width.
You can use the DBF Create tool to change the format of the Shapefile DBF files.
This error during data transfer in the GIS Layer Transfer Wizard while searching for duplicate key values in source tables, is caused by a non-conforming Shapefile, probably one created by an application other than ArcView. Open the file in ArcView, and convert it to a Shapefile. Then try running the Layer Wizard again.
The index file has likely gotten corrupted. Delete, move, or rename the .NDX file.
This error appearing during data transfer in the Layer Wizard program is caused by a mismatch of the number of entities in the Shapefile database (DBF) and drawing file (SHP). Option 1: Add records to the database, to create a balance between the 2, and then use the Layer Transfer Wizard. Option 2: Transfer the SHP file only into Hydra, with no associated records. Hydra will create a blank SY_.DBF file. You can import any data from the original Shapefile DBF using an external database.
Your Shapefile DBF may have a problem with field type. For the mentioned field name, try changing it from numeric to text, or visa versa, using the database tools available. Then try running the Layer Transfer Wizard again.
Check the name of your Shapefile. The Transfer Wizard does not allow use of “-” or other non-character or numeric names, and is limited to 8-character names.
Delete the index files [databasefilename].SHX, .NDX, and .INF, using File Explorer. Try running Layer Wizard again. (the index files will be re-generated).
Compare the number of characters in the fields in your Shapefile DBF to the fields widths of a Hydra database file. Make adjustments to the data in your Shapefile as necessary.
There may be a space in the ID or Key data. Try changing the ID data format. You may find the database tools to be useful. Then try running the Layer Transfer Wizard again.
If you have a layer in AutoCAD Map 2000 with identification numbers stored in object data, you can import it into Hydra using the Layer Transfer Wizard. First, convert the object data identification numbers to a text layer. Then save the file as an AutoCAD 14 format DXF file. Then, using the Layer Transfer Wizard, for your GIS Key Location, select “Text Layer”.
If you have the choice of using AutoCAD, GISMaster offers a cleaner alternative way to update data while maintaining your existing G_ID numbers. However, if you need to use ArcView for this, there are many different ways to accomplish this result. Here is one way:
- In ArcView, put your new pipes onto a separate layer from your existing ones.
- Create a Shapefile of your new pipes. Use Layer Transfer Wizard to convert your new pipes to a Hydra DXA/DBF file.
- Take note of the highest G_ID# in your existing system. Open each of the DXA and DBF files in Excell, and add that highest G_ID# to the G_ID#’s of the new pipes files.
- Add the data from the new pipes files to your existing Hydra files. You can copy/paste the DXA data in a text editor, and concatenate the DBF records with a database program.
- Open the modified layer in Hydra. Re-do topology, SE connects, and flow files, as necessary.
As another alternative, if you are only updating the data, and not graphical entities, consider doing an update query in Microsoft Access.
Some field lengths or field types in your database file (.DBF) do not conform to dBASE III requirements. For example, you may have a numeric field longer than 20 total characters, too many decimals, etc.
The type of data in a source field is incompatible with the target field. For example, you may be trying to put character data into a numeric field, or the data is too long for the target field.
A good way to troubleshoot this is to compare your [Shapefile].DBF side-by-side with a [Hydra].DBF from the sample data. Use the WCREATE utility (on install CD) to view and modify the field types and lengths.
Only [Shapefile].DBF and .SHP are required for transfer, and other index files can cause problems. Remove extraneous files from the source folder: [Shapefile].SBN, .SHX, SBX, NDX, INF
Open your Hydra .DXA file in a text editor, such as NotePad, WordPad or TextPad. Scroll to the end of the file and delete the word “END” in the last line. Save the DXA file, and try the Transfer Wizard export again.