Epale Alex,

I think you need something a bit heavier than a bizobj, but at the same time it doesn't need all the intelligence inherent to a bizobj.

From what I've learned so far, just create an object that has a private data session.

Give it a couple of properties you will need: the employee's id and then others that will hold the result.

Your could use the init method to read the emp_iid property, do the calculations and store the results in the other properties.

Remember to close all used tables upon destroying the object.

It's quick and dirty and unpolished, but I think this little recipe should be enough to get you started (or at least asking questions).

ave fun!

Ale


>Hi,
>
>A routine sums several kinds of overtime hours that a worker has worked on various dates. In FPD 2.6 I would define private variables either in a form setup or at the beginning of a process and accumulated in those. Since the routine is called from different places, form properties are not a solution and it sounds like a case for a business object!!
>
>What can you folks in the UT tell me regarding business objects? What is the best way to create and organize them. They either need to be public, passed around or "attached" to the app object. What are the best practices ?
>
>TIA,
>
>Alex