<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ArcGIS 10, SP4 VBA String Variables limited to 250 characters long in ArcObjects SDK Questions</title>
    <link>https://community.esri.com/t5/arcobjects-sdk-questions/arcgis-10-sp4-vba-string-variables-limited-to-250/m-p/658296#M17694</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I have determined that VBA does not have a 250 character limit as I originally thought.&amp;nbsp; I was mislead into thinking that by using a watch variable, which does have a 250 character limit, but the string variable itself did not have this limit.&amp;nbsp; I was able to demonstrate the string was not truncated by using a Msgbox output.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have determined that my problem was due to a change by the DBA to the way values were stored in a field.&amp;nbsp; The change (removal of leading spaces from the values of a text field) caused my query string to be invalid and fail.&amp;nbsp; I was not notified of the change, but eventually discovered the alteration.&amp;nbsp; By changing my code to trim out leading spaces in my query string values and conform to the current field values I have resolved my problem.&amp;nbsp; Sorry for the faulty interpretation of what I thought was my problem.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;To repeat, VBA strings at ArcGIS 10 do not have any change to the number of characters that can be stored relative to any previous version.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 11 Jun 2012 15:15:15 GMT</pubDate>
    <dc:creator>RichardFairhurst</dc:creator>
    <dc:date>2012-06-11T15:15:15Z</dc:date>
    <item>
      <title>ArcGIS 10, SP4 VBA String Variables limited to 250 characters long</title>
      <link>https://community.esri.com/t5/arcobjects-sdk-questions/arcgis-10-sp4-vba-string-variables-limited-to-250/m-p/658295#M17693</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;For some reason, VBA scripts I have used for years can now only store 250 characters in a string variable.&amp;nbsp; I know that String variables used to be ablle to hold at least 2048 characters.&amp;nbsp; I have used a watch variable and verified that string variables stop appending charaters after 250 characters have been added to the string.&amp;nbsp; 250 characters is too short to create many of my WhereClause Strings and causes many of my VBA feature selection queries to fail.&amp;nbsp; My VBA scripts continue to work as long as all of the strings created in the script are 250 characters long or less.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I think this limitation may have been introduced with ArcGIS 10, SP 3.&amp;nbsp; Can anyone else test whaterver ArcGIS 10 Service Pack they have and report the maximum number of characters they can store in a VBA String variable?&amp;nbsp; I need to know the last Service Pack where strings held about 2,048 characters so I can roll my installation back (at least until my scripts are converted to VB.Net).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I originally thought I had installed SP 4, but in fact I am using SP 3, so that is where the limit seems to have occurred for me.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 May 2012 19:58:29 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcobjects-sdk-questions/arcgis-10-sp4-vba-string-variables-limited-to-250/m-p/658295#M17693</guid>
      <dc:creator>RichardFairhurst</dc:creator>
      <dc:date>2012-05-23T19:58:29Z</dc:date>
    </item>
    <item>
      <title>Re: ArcGIS 10, SP4 VBA String Variables limited to 250 characters long</title>
      <link>https://community.esri.com/t5/arcobjects-sdk-questions/arcgis-10-sp4-vba-string-variables-limited-to-250/m-p/658296#M17694</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I have determined that VBA does not have a 250 character limit as I originally thought.&amp;nbsp; I was mislead into thinking that by using a watch variable, which does have a 250 character limit, but the string variable itself did not have this limit.&amp;nbsp; I was able to demonstrate the string was not truncated by using a Msgbox output.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have determined that my problem was due to a change by the DBA to the way values were stored in a field.&amp;nbsp; The change (removal of leading spaces from the values of a text field) caused my query string to be invalid and fail.&amp;nbsp; I was not notified of the change, but eventually discovered the alteration.&amp;nbsp; By changing my code to trim out leading spaces in my query string values and conform to the current field values I have resolved my problem.&amp;nbsp; Sorry for the faulty interpretation of what I thought was my problem.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;To repeat, VBA strings at ArcGIS 10 do not have any change to the number of characters that can be stored relative to any previous version.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Jun 2012 15:15:15 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcobjects-sdk-questions/arcgis-10-sp4-vba-string-variables-limited-to-250/m-p/658296#M17694</guid>
      <dc:creator>RichardFairhurst</dc:creator>
      <dc:date>2012-06-11T15:15:15Z</dc:date>
    </item>
  </channel>
</rss>

