Comments on: Describe Your Actuate Experience

By: Tobi

Tobi — Thu, 08 Oct 2009 12:55:05 +0000

I’ve got report #1 that uses view A. Report #2 is similar to the first, but uses view B, same dozen or so heading fields, different details. So I change the data source, maybe remove the details that are different then do a build, which brings up the whole list of common fields which all need to be changed to reflect view B. Then repeat for reports #3, 4, 5 … Tedium, but as I say, job security.

By: Douglas

Douglas — Thu, 08 Oct 2009 01:18:02 +0000

@tobi I find Actuate frustrating at times as well. But I’m curious about what you mean by “field-by-field when the view…changes”.

By: Tobi

Tobi — Wed, 07 Oct 2009 20:24:32 +0000

I’m a learn-by-doing professional who grew up with Access in the ’90’s and has moved into using Actuate with Oracle in the last couple years, working with a “get official training and go by the book” developer. While I have learned how to get things done, I find Actuate extremely frustrating in its retention of parts no longer needed and the need to go field-by-field to get values when the view behind the report changes. And subreports and libraries, ga-a-a-ah! I can make them work, but could put together an Access report in a fraction of the time needed in Actuate. I seem to have job security here, but I’m enjoying it less!