I have a sneaky suspicion that he means a fex on his desktop. If that is the case, RSquared, then the answer is no unless you have a full funtioning version of WebFOCUS running on your PC.

Nope, not on the desktop, but on a server. The user signs on to a Launch page that is DevStudio. The Launch page then executes an Html file that has the Webfocus in it. When I try to drill down to a .fex that is in the same project folder. I get an error message.
(FOC227) THE FOCEXEC PROCEDURE CANNOT BE FOUND:
SEC-DailyNewCasesSummaryReportCasetype
(FOC227) THE FOCEXEC PROCEDURE CANNOT BE FOUND:
SEC-DailyNewCasesSummaryReportCasetype

It's not exactly clear how you're environment is working. Users don't sign on to launch pages in DevStudio. Is every user running their own version of DevStudio pointing to a shared project on a network? Normally the launch page and fex files are either in a WF server application directory or within an MRE environment - both of which can be accessed through DevStudio, but are not in nor part of DevStudio. In any case, the fex name that you are searching for is probably a property of the fex (you can call them whatever you want) but is not the actual name of the fex. WF does not like dashes in fex names. and they are usually shorter names. Fexes you've created via DevStudio are given an eight character name. The actual name can be seen by right clicking the fex and selecting properties.

Darin,

Sorry, I left out or typed over a line. The user signs on to the server using a javascript process that executes the launch page. BTW when I click on the properties, the name is
SEC-DailyNewCasesSummaryReportCasetype.fex and the locations is
IBFS:/PCFNASCENT/DEV/secretaryreports/

If you are getting procedure not found, that is because the focexec you are drilling to is not in the default path. You can add the IBIAPP_app parameter to the stylesheet syntax to point to the directory where the program is. Then your URL will be generated correctly.

There are lots of examples of how to do this on this forum. Please search for IBIAPP_app.

Darin,

The 8-character limit for focexec names is strictly for MRE and I think has been lifted in 764. R is trying to run a self-service focexec.

But your point about the launch pages being in the web server path is well taken.

R, are you doing remote development either through Projects or Data Servers? Please explain your archtecture further.

Ginny,

All the .fexs and .htms are in the same DevStudio Project tree. The way we are trying to work things around here is to have all the bureaus sign on the same way. The cick on an icon that invokes a Java process that validates the User and then sends them to the appropriate Launc page, which resides in the DevStudio project HTML files folder. The Launch Page then executes other HTML pages, which contain the WF code. These part work OK. We only have a problem when we try to drill down from one of these HTML reports. The message if FOC227.

Thanks

RR

RR, If you are getting a FOC227 then my original post states the problem. WebFOCUS cannot find the focexec it is looking for. When you do a drill, it starts up another agent and if that agent doesn't know the path or location of the child report because you didn't specify it on the stylesheet syntax or it is not in the profile of the server or the user, then it will not be able to find the program.

Please check into this.

I probably don't understand your whole environment, but from what you describe, what you are trying to do does not fall within what a Dev Studio license allows. Dev Studio is intended for single, local user development and running of procedures. Multiple users should not be "logging" in to a devStudio environment to run reports. What you are able to do and what you are allowed to do are two separate things.

Let's be clear. If the fex is in the local projects tree of Developer Studio, the fex resides on an individuals desktop or a shared drive. As Darrin says, the licensing for Developer Studio doesn't allow for this as it is intended for single user development only. If the fex resides in the WebFOCUS Environments tree, then if in the Data Servers area, the fex resides on the WebFOCUS Reporting Server. The caveat, is if the fex is in the localhost (or individual's machine name) data server, then again, it is local to that PC. It is odd that any customer would drill back to an individuals workstation. If the fex is in the localhost tree, just move it to a WFRS that is not on the local machine and ensure that the application is in the app path and the fex should be found. MRE is a different story. If you're trying to drill to MRE, there is an MR cookie that gets loaded when you authenticate to MRE. You cannot drill from Self service to MRE, as you've not authenticated. I'm sure that there are ways with custom security programs, but it seems like entirely too much work for the benefit received.

Hey Folks,

After working with IBI Tech Support, I was able to get this Beastie going. Yes, it was a APPPATH issue and we came up with 2 solutions, first was to move all the drill down fex to baseapp, and the other is to add a line to the first WF code,
APP PREPENDPATH seclaunch

Thanks All

I knew it!

Ginny,

I kinda knew it too, but I just couldn't find a way to make it work, until today. BTW IB is still trying to find out why the other solutions, such as the one you suggested, does not work.