SAPGui 7.30 on Windows-7

[Former Member]

SAPGui 730 Installation on Win-7 and histroie files from SAPGui 7.20

the migration of GUI 7. 20/XP on GUI 7. 30/WIN 7 has historical files, user files and application history like Abap editor files.

Are the GUI 7.20 historie files importantly  for the installation of SAPGui 7. 30.

c:\documents and attitudes\user name\application data\SAP\SAPGui\History\

Providing 7. 20 to a new installation SapGUi 7. 30 from the SapGui to sure and for this one on Win 7.

Briefly sought-after: Are the old historical files important from 7. 20   to  SapGui 7. 30 under Windows 7 ?

[Sriram2009]

Hi Michael

  Yes you can bring the history from old SAPGUI 7.20 to SAPGUI 7.30 for that Kindly follow the steps

1. Take the backup of SAPHistory (User id).mdb file from old windows XP to new Windows 7, file located on C:\Documents and
Settings\(User id)\Application Data\SAP\SAP GUI\History\SAPHistory(User id).mdb

2. After installed the SAPGUI 7.30 version on windows 7 rename the file SAPHistory (User id).mdb

(File located on C:\Users\ (User id)\AppData\Roaming\SAP\SAPGUI\History\SAPHistory (User id).mdb)

3. Copy the file from old windows Xp to windows 7 and then check the SAPGUI history.

Note: We using SAPGUI 7.30 with SP level 3

Thanks

Sriram

[jude_bradley]

Hello Michael,

It's not possible to transfer history from one machine to another consistently.

However,while we're on the subject,please be aware that there is a SAPGUI bug in patch 5 regarding

history which will be fixed in the up-and-coming patch 6.

[Matt_Fraser]

Interesting.  We are just starting to finally roll out 7.30 here, and on our support team (read, guinea pigs), I had just one developer complaining about how his field history stopped working after upgrading from 7.20.  I spent a lot of time working on this, with clean sweeps and reinstalls, windows updates, everything, but in the end what fixed it was discovering that he had Office 2010 64-bit installed by mistake.  We removed that and replaced it with Office 2010 32-bit and that fixed the history bug.  Nobody else had this problem, but no one else had 64-bit Office.

We are on patch 5.

--Matt