Report generation on notes client

We have a notes database enabled both for the client and web browser. A typical functinality is required on both notes client and web to generate a weekly report.

The report needs four checkboxes on each row along with some other columns, either ticked or unticked depending upon certain criteria. Each row represents data collected from 1 to 4 different documents.

We generated the report for web using an agent, which generates HTML in the required format. Can any body guide me on the approach to be used for Notes Client? We do not want to use Notes Browser. This functionality is required on plain notes client. The main problem which we are facing is to display dynamic checkboxes on notes client either ticked or unticked

Hope I have made the requirement clear. Any help will be greatly appreciated!

Thanks

Subject: Report generation on notes client

Not do-able in the Notes client, at least not in any sort of non-destructive way. Generating fields on the fly would require design access to the database (not generally a good idea). There will definitely be conflicts, and eventually there will be no way to predict the “start state” of the form. If you are willing to bend that far to reach your solution, then you’re stuck with the problem of unique fields in the database. Because of the way you’re putting this together, each check box would need to be a separate field. It would not take much reporting activity before you really start to get into trouble.

Lose the checkbox, and use a text “checkbox” using one of the symbol fonts. This would not have been possible in R5 without a LOT of chicanery. Change the font to the appropriate one when it’s time to create the box, and write the appropriate character to the table. It won’t be functional (i.e., it can’t be checked or unchecked by the user, and it won’t look quite the same as the field version would) but it would be a good screen-or-print read-only solution.

Subject: Report generation on notes client

Hi, I think I just did something similar.

If I’m right you either have a field(then computed text) or a embeded view in which you pass the HTML via agent to the web browser. I also passed an extra field and read the changed or not changed values in with “this” in javascript. It’s the only way I found I could reference the HTML code. I then populated another field with altered HTML, performed with an agent, and saved both the js altered field and agent altered HTML. Both will work on the client side, but if you need dynamic field values you may(I don’t know) only be able to use the js edited field.

I know that’s confusing, if you need me to clear it up I’ll try, but right now it’s quiting time.

GL!

Ben