Solution : https://service.sap.com/sap/support/notes/199527 (SAP Service marketplace login required)
Summary :
Issues with the input history not displaying in SAP GUI 620 require investigating various prerequisites and configurations. To resolve, ensure SAP GUI patch 20 or higher is applied; Microsoft components MDAC and MSJET must be properly installed. In Windows, users should log in with a user name and ensure the machine is named. For SAP Logon, the low-speed connection setting should be unchecked per Note 161053. For technical details, MDAC and MSJET versions post-MDAC 2.5 need separate installations. Set local data under GUI options correctly, considering file sizes and entry limits. Unresolved issues may need trace file analysis or further checks on MDAC installations.
Key words :
[trace] mode=0x00000307 components=local db, microsoft knowledge base article q169395, microsoft knowledge base article 271908, check mdac/msjet installation, microsoft component checker, contact microsoft support, microsoft components mdac, low speed indicator, multi-threading architecture, locally stored database
Related Notes :
| 1176026 | History: doesn't work even after MDAC repair (note 931540) |
| 931540 | History: repair MDAC installation |
| 919321 | EP6: How to set WinGui to run in Low speed connection mode |
| 705052 | Input history for SAP GUI for Windows 46D |
| 620677 | History: No history available due to ADO installation issue |
| 568119 | Change of the local entry history to ADO |
| 399180 | SAP GUI input history depending on field (name) length |
| 161053 | Using SAPGUI in WAN |