ArcReader 10.0 Find tool Issues

[ModernElectric]

Greetings-

   Our company does things a little different. Instead of using ArcGIS Server and web development, we use ArcMAP as our editor and ArcReader as our viewer. I have been getting complaints from different users inside my company that ArcReader 10.0 is unreliable.

   The largest complaint I get is when they use the "FIND" tool. Sometimes it comes up fast. BUT, most of the time it takes a few minutes for the FIND dialog box to show up. Other times - ArcReader 10.0 completely freezes up and they have to force close it and reopen it.

   Is this a known issue? Also - Does ArcReader 10.1 and/or ArcReader 10.2 have a better FIND tool and is the new release(s) more reliable than ArcReader 10.0?

Thank you

[JustinRichardson]

I posted this a few months ago in a different thread:
The problem is that the find tool tries to connect to online services.  You can disable these in the DefaultLocators file.

Here are the instructions for disabling the Find Tool�??s function to check ArcGIS Online. The file you need to edit is located here: C:\Program Files (x86)\ArcGIS\ArcReader10.1\Locators\DefaultLocators.xml

-Open the Default locators.xml file.
-It can be opened in any editor by using open with (Notepad, Notepad ++) -Comment out the tags with ArcGIS Online Locators by adding <!--... --> at the end.
(For example:
<!-- ArcGIS 10 Online US Streets geocode service -->
<!--locator_ref>
<name>Locators/TA_Streets_US_10</name>
<display_name>10.0 US Streets Geocode Service (ArcGIS Online)</display_name>
<workspace_properties>
<factory_progid>esriGISClient.AGSServerConnectionFactory</factory_progid>
<ags_connection_properties>
<url>http://tasks.arcgisonline.com/arcgis/services</url>
</ags_connection_properties>
</workspace_properties>
</locator_ref-->)

Also here is the web help link for the same:
Setting default locators in ArcMap
http://help.arcgis.com/en/arcgisdesk...0040000000.htm

I actually comment out all external references to locators. The find tool now opens INSTANEOUSLY!
Thanks to ESRI Customer support for helping me figure this one out.