nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

error calculating a field using field calculator

ChristiNelson1

Hi there,

I have an attribute table and have added a new field (AQU_PIPE_NAME). To populate its selected fields, I would like to set it equal to the selected values in another field of the same table (EXTENSION). I have made only the selected fields visible. I ten right click on AQU_PIPE_NAME and click on Field Calculator. I set the following operation: AQU_PIPE_NAME = [EXTENSION] and receive the following error message:

"There was a failure during processing, check the Geoprocessing Results window...
Calculate Field [133038_10132011]
ERROR 000732 Input table does not exist or is not supported

Its a simple file .gdb attribute table. Not sure why it wouldn't be supported. No subtypes exist on this table and I made sure.

Helllp!
Christi

Encuentra más publicaciones etiquetadas con

Accepted answers

All comments

SamCoggins1

This maybe a dumb response. Does the new field support the data type you're trying to add to it? For example, you're not trying to add data from a text field to a short integer field are you?

JoshThompson1

I have found that ArcMap 10.0 is very sensitive as to how you name a layer in your Table of Contents.

So far I have found two instances of where I get an error when using the field calculator:

1. If your layer name in the Table of Contents has extra spaces at the end. (Fix: remove any extra spaces)

2. If your layer name in the Table of Contents has has a slash "/". (Fix: remove "/")

If you suspect that you might be running into this issue, try renaming the layer.

I don't know if Service Pack 3 will address this issue as I have not yet installed it.

Josh

SaraJK

2. If your layer name in the Table of Contents has has a slash "/". (Fix: remove "/")

Thank you! This solved my problem! I also had a slash in one of my coded value domains and got the same error. I removed it and it was working again.

GeorgiaJackson

Is really a good question

JacksonTrappett

Thanks - this fixed it for me as well!

DanThompson

thanks this was driving me crazy. i knew my field types matched and couldnt figure out why i was getting the error

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.