IS THERE ANYWAY TO TRACK IF SOMEONE HAS MADE A CHANGE TO A FEX FILE. LIKE SOME SORT OF AUDIT TRAIL IN WF. I AM USING A APP QUERY WHICH GIVE ME THE DATE OF THE CHANGE BUT NOT A USER.
THANKS

Hi Chuck,
IBI has a tool, Resouce Analyzer, that will do this for you.
Rich

Resouce Analyzer is not a source control or audit tool and unless it has changed
it does not have the capability to give the sort of information Chuck-n-Charge is
wanting to see.

It's purpose is not to audit who changed requests rather who ran requests and what they requested.

To do what Chuck-n-Charge wants a third party tool is required.

JG
Any suggestion on the third party tool?
Thanks

I think you can set up something like Visual Source Safe to do version/source control.

How deep is the pocket?

IB's position.

"Developer Studio supports third-party source file management products such as Microsoft Visual SourceSafe, PVCS Version Manager from Merant, and others that use an industry standard API. Source file management (called source control in Developer Studio) provides version control for your individual projects and for your team projects, allowing multiple users to work on the same files without overwriting each other's changes. A source control product manages access to source code and documents all code changes.

Developer Studio provides access to basic source control functions through menu options in the Explorer. If your site has installed a supported source control product, you can track the history of project code without leaving your development environment.

Source control is available from the Projects on localhost area in the Explorer. It does not apply to files in the WebFOCUS Environments area."

I'm sure there are a lot of different opinions, about what to use, which is best, and which works best with WebFocus.

I only use them when the client has a requirement that they are used.

Other people’s advice and experience would be of a lot more help than I can suggest as they undoubtedly have much more exposure and practical experience.

Perhaps a general discussion on 'source control' might be an idea.