ebaptist
Full Member
  
Karma: +1/-0
Offline
Posts: 22
|
 |
Re: IE8
« Reply #2 on: February 18, 2010, 12:00:20 PM » |
|
To achieve compatibility with Internet Explorer 8 for Active Access 5.9, you need to set a registry key. Follow the steps below: 1. Apply Rich client 5.9 SP04. 2. Set an IE8 registry key for all the end user computers running IE8 so that IE8 will use the same process for all tabs, frames and pop-up windows in each browser session. Please note that you can also deploy the registry change through Group Policy. I. Close all IE windows II. Open registry editor III. Go to the following key and select it 'HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main' IV. Check if a value of type DWORD with the name 'TabProcGrowth' is already defined on the key i. If it is already defined set its value to 0 ii. If not, right click on the key 'Main', select 'New' > 'DWORD Value' and set its name as 'TabProcGrowth' without quotes and value to '0'. This information is also contained in Knowledge Base article #10840. This service pack has the following additional features: • The new functions AddAttachment and AddBLOBAttachment, which are exposed through IRStealthLetterExpress4, have been provided for adding attachments to LetterExpress at client side. For more information, see Knowledge Base article # 10834. • A new argument has been added for the OnSRLSegmentItemClick () notification, which exposes the search event object. For more information, see Knowledge Base article # 10835. • new property DisableAutoPopup, which is exposed through IRRecordSelect8, has been added, which will disable the auto popup behavior of foreign key fields. For more information, see Knowledge Base article # 10837. This service pack resolves the following issues: • Bar graphs displayed incorrect results for Italian regional settings • Secondary paging displayed incorrect results. • Apply failed for modal form for specific conditions. • The registry key displayed an incorrect Service Pack number • Specific forms such as company, contact and leads failed to load • Portal queries were executed twice for each SmartPortal query item. • The FocusField API did not work correctly for Secondary segments
|