MACRO issues in QV 9.0 SR2

[Anonymous]

Hello all, We have been looking to Upgrade from QV 8.2 to QV 9.0 SR2 and have run into some problems with macros we developed.

In the attached qvw, I have a simple test button that should bring bring up a message box that contains the 'DOMAIN\username' data element using the ActiveDocument.GetLayout.AuthenticatedUser. It works fine in QV 8.2, but brings in a blank message box in QV 9.0.

We use the DOMAIN name to help decide what data is scrambled for differing logins, and we need to get this value. It has been submitted to QV and we have gotten back the perverbial "Works as Designed". It is being worked by another QV support element yet.

I am hoping that someone out there has this issue and either found a checkbox or a workaround. We have other Macro Functions that have the same behavior, so it is not limited to the statement above.

Thanks,

JS

Additional: The macro above does work on the QVS 9.0 accesspoint. Hmmmmm.

[Oleg_Troyansky]

Not sure why the function is not working as it did before... As a possible workaround, the QlikView function OSUser() still seems to work properly, at least in a local Developer tool. Test it via the Access Point, though...

[Anonymous]

I had thought about that, but the problem is I need the value in the marco. OSUser() produces the correct result in the text object but I am not sure how to pass it to the macro. The macro is where I do all the data scrambling.

I have another macro that reads a value from a input box but they are also coming up blank. Did you find the same results with my test file?

Thanks,

Jerry

[Anonymous]

This has been identified as a bug. Thanks.