Latest Contributions by CoyPotts1

Whenever I tried it exactly as you have it typed in your example, I get the following error. ... View more

I have background GP disabled.  I leave it like that because there are parts of my script that export a table to an Excel sheet, and the tools for Excel functionality are not compatible with 64bit processing.  Details on that are here. I added a script tool to a normal toolbox that references the .py document. ... View more

From what I can understand of your example, which may very well be incorrect, is that the result would fill the desired field with the literal text string of " + region + ", instead of the two digit region abbreviation that the mapName[:2] gives me.  In the example I pasted in my original posting, if I use 'region' or "region" instead of just region, then it runs through just fine and updates my field with the literal string that I quoted, and not the value given to region earlier in the script. ... View more

Duly noted for future reference.  I ended up resolving the issue, though.  Please see the code pasted below.  Thanks again for your help in this thread and all others.  I've seen your name quite a bit in some of my threads, so thank you for all of your time. ... View more

I moved past this portion of the script and on to a different part that pulls the feature classes exactly how they are in the map and does the exact same thing (TableToTable and then TableToExcel).  That part works just fine, so I'm thinking that there's no compatibility issues going on. # Export TableToTable & TableToExcel # Set Local Variables exportTable = updatedTable # This table is the result of the summary statistics tool in the previous step exportLoc = kmfFolder + "/" + outKMFgdb outTable = "general_KMF" outXLS = "general_KMF.xls" # Execute TableToTable arcpy.TableToTable_conversion(exportTable, exportLoc, outTable, "", "", "") # this part works fine # Set Local Variables inTable = outTable # hoping to grab the result of the TableToTable function above # Execute TableToExcel arcpy.TableToExcel_conversion(inTable, outXLS) In this instance, the TableToExcel keeps kicking back saying that the file type is invalid just as it did before, though.  I've tried various ways of setting the inTable variable in line 13, but none of them have worked.  I also tried to create a table view between the two tool functions and it still said invalid file type.  I can't hard code the variable name because the location will be variable depending on the name of the map.  Essentially the kmfFolder variable grabs the maps file location and adds a few characters that are standard between maps, and that is where everything is saved for the current map document. Examples of what I've tried using for the inTable variable: inTable = outKMFgdb + "/" + outTable inTable = exportLoc + "/" + outTable inTable = (combo of all above) + "/general_KMF" inTable = (combo of all above) + "/general_KMF.dbf" etc... *NOTE*:  I intend on implementing the os.path.join suggestion mentioned above, but I'm just trying to get it working for now.  Since the method I am using works in other areas of the script, especially in areas that due essentially the same thing, I don't think it's what's causing this particular issue. ... View more

Okay, that makes more sense now.  Thanks for the clarification.  ... View more

I have background geoprocessing turned off, so I'm wondering if this isn't the issue.  ... View more

This may be getting me in the right direction. The feature class that I am using has duplicate fields for each customer, so say each customer has the same 20 fields, and the only difference between them is their customer identification. I want to loop through and say something like the following: if Customer1NodeID != None:      return regionvariable if Customer2NodeID != None:      return regionvariable if Customer3NodeID != None:      return regionvariable else:      return None I'm just not sure how to nest multiple fields to be updated into one loop.  Essentially I have 5 customers that I want to add data to their respective fields, but only if their NodeID field has data in it, otherwise leave it blank. ... View more

I am indeed using 64 bit background processing.  Do you have any suggestions as to a workaround that doesn't result in me and everyone else that would use this tool having to install 32 bit libraries on top of the 64 bit libraries? Thanks! ... View more

Good catch, Darren. Blake, how would I construct this when I am using variables and added strings?  I didn't fully understand the examples in the provided link.  Also, why would concatenating strings be unreliable?  Just trying to understand. Thanks to both of you! ... View more

I am taking a feature class and running the Table to Table tool to save it as a data table.  Then I am taking that data table and exporting it to Excel. ... View more

I'll have to play around with the table view. Essentially I am porting over a very large model builder model.  Following the workflow in order as it is in Model Builder, I just used the same table name thinking it would work.  I'll try this with the table view option when I get a little more time to tinker with it and I'll respond with my results. Thanks! ... View more

Actually, I made an oversight when I pasted my code.  I omitted some of the verbiage to not include customer names and whatnot, so instead of each NodeID field literally having a number after it, each number actually represents a customer name.  But I will still use your sample code as reference for a FOR statement!  . Can you think of a way to do it without the FOR iteration? ... View more