Hi,

I'm running into an issue with a user here and am wondering if anyone has seen this and perhaps has some advice.

* User is currently using Dev Studio 766 and has a WF 766 environment.

* User created a new fex that uses an Oracle stored procedure for data gathering.

* When the fex was first created, the user was then able to access Report Painter to create the Table File piece against the output that will come from the stored procedure. Saved and closed the fex.

* The next time (and every time afterwards) the user opened the fex, the report component does not appear in the report viewer, so user can not access this piece with the Report Painter (to make changes or whatever).

* I tried to reproduce this issue using my 769 version of Dev Studio and am not having the same problem. I am able to see and access the Table File piece from the report viewer with no problem. Report Painter opens up and I can see the columns that are meant to be supplied by the stored proc.

Our first inclination is to tell the user to upgrade their Dev Studio to 769. However, they are going to be using this against a 766 environment and are in the POC stage of development and probably won't be looking to upgrade the environment for a good while.

So, my questions are:

* Are there any potential problems or other technical implications with using Dev Studio 769 for a 766 reporting environment.

* Has anyone heard of this problem using Dev Studio 766 with stored procedures? Any work-arounds or other advice with this issue?

Environment details: Dev Studio - 766 (vs 769) / Platform - AIX / WF environment 766.

Thanks in advance for any input!

-Debbie / Fidelity - NH

This message has been edited. Last edited by: Kerry,

Debbie,
Although I have not seen this behaviour of DevStudio myself, I think that the only thing that can cause this is security settings on the machine that holds the procedure. I did see situations where the user was able to create a file and store it on the system, but was not able/allowed to change it once it was created. This kind of thing may be the case here.
Upgrading to another version of DevStudio will not solve that.
On the whole, it is not advised to use a DevStudio release that is more advanced than the WebFOCUS client/server software used. The other way around usually (but not always) present no problems.