Back in the ArcObjects days I had no problems creating field names that start with a number. Now when I use Geoprocessing.ExecuteToolAsync("AddField_management", mva), it restricts me from using field names that start with a number (or underscore that I have read). Any way around this? Wonder why the restriction now when all my legacy data has many fields starting with at number?
Thanks for the link. I did see that. I wonder if they just started to enforce it as legacy apps (ArcMap) do allow it (for shapefiles at least). I now have make sure my code works with the older field names and new ones I will make up. Ugh, more work!
