I am having a problem where I coded A drill down, which works for the most part. The problem is for certain users, the drill down URl that is returned begins as file://XXXX instead of http://XXXX. The later is the correct way for the URL to appear and launches the report as expected. The former is incosistant with the URL format and returns an error. I would not call this random but it is correct for some users and not others. Any body know how to fix this?

PS. this wouldn't be mime-type problem would it?

When you say it's happening for some users, do you mean it's happening on some user's workstations?

Are you drilling down to a WebFOCUS program or an HTML file or some other kind of file?

How is the drilldown link being created?

Is this in MRE or a self-service application?

Sorry I should have been more detailed....

It is a PDF report drilling into another PDF report. I have discovered that it is an Acrobat 7.0 problem.

Does anyone know a workaround for drilling down in acrobat 7.0?

Looks like a bug in WebFOCUS:

TABLE FILE CAR
SUM SALES BY COUNTRY
ON TABLE PCHOLD FORMAT PDF
ON TABLE SET STYLE *
TYPE=DATA, COLUMN=COUNTRY, FOCEXEC=SSS (COUNTRY=COUNTRY), $
ENDSTYLE
END

Doesn't generate the correct URL for the drilldown

Yes, that is the isssue. BUT, I beleive it is an Acrobat 7.0 that has the 'BUG'(feature maybe?), because the same code(including your test code) that fails on my machine runs fine on a machine with Acrobat ver. 6.0.

Any one know a work around?

We use WF 5.2.5 with Acrobat 7 and we had to add

-* make sure all drill-downs get the full URL
-*
SET FOCEXURL=http:///ibi_apps/WFServlet

where you replace with whatever your URL is for that

and it correct that issue.

sorry - looked like a tag to the software:

-* make sure all drill-downs get the full URL
-*
SET FOCEXURL=http://www.compname.com/ibi_apps/WFServlet

where www.compname.com is whatever your URL is for that

quote:

SET FOCEXURL=http://www.compname.com/ibi_apps/WFServlet

Drew, thank you for that piece of information.

Problem Solved.....

It is actually an Acrobat Bug. Upgrade to version 7.0.8 and the problem goes away.