cancel
Showing results for 
Search instead for 
Did you mean: 

Workbook error in GUI 7.20

Former Member
0 Kudos

Hi,

We have just upgraded to SAP GUI 7.20 and have office 2007 with windows 7 on our computers.

Now, when we are changing old workbooks (developed in GUI 7.10) with standard BEx buttons, we are getting an error: error in loading dll when executing the buttons.

When I am design mode, I get the error:

The BEx Analyzer cannot generate VBA code due to the security settings.

The security settings in my office are set to trust visual basic.

Any other things, I can try?

Br,

Sonni

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Good day,

Please check if the followiing SAP Notes are helpful for you ...

1570297 BExAnalyer- No response to toolbar - Registry key issue

1540331 Installation & Uninstallation scenarios of BEx frontend

1535594 BW Frontend(7.X)-Upgrade scenarios in different GUI(710\720)

1430516 BI Frontend - Versioning methods of the library files

Best regards,

Karen

Former Member
0 Kudos

Hi,

These are internal SAP notes and I don't have access.

However, after rebuilding the workbook in 7.20 everything worked fine.

Br,

Sonni

Former Member
0 Kudos

Hi Sonni,

Good to know the problem was resolved.

Only the first listed Note is 'In Process' -- it is being updated.

Please keep an eye on these Notes as they are helpful for identifying what should nad shouldn't work within the newer releases,

Kindest regards,

Karen

0 Kudos

Hello Sonni.

What you mean when you said "after rebuilding the workbook in 7.20"??

You have created a new book, or repaired the old in 7.20? If repaired, what exactly did you do?

Answers (1)

Answers (1)

0 Kudos

Well, I fixed my books, I've done this - in GUI 7.10 removed from the book all the buttons, from VBA project has removed all of the handlers of buttons, exported and deleted from project all the modules - delete all the code in the project in my case - and save the book. Then at 7.20 opened the book, added a buttons with the same functionality that was, imported saved modules (without any changes), and save the book. The error is gone.

Former Member
0 Kudos

Hi,

I just made a new version of the workbook in 7.20 and deleted the old version. This was easier for me.

Br,

Sonni