I am trying to create a programmatic table that behaves like a view. I have read LOTS of documentation but unfortunately the specific details as to how to do this has been elusive.
I have an embedded view that as we all know will not print ALL of my documents if I reach a certain document count. I can very easily have a couple of hundred docs that would return to that embedded view and I would in turn need to print them (in view format - not he docs). This is my need for a programmatic type table. If I can create this type of table (which it sounds like several of you already have), I will be able to print all the docs (as a view) with no problem.
Here are my problem areas:
Do I use a regular table or programmed table?
Are there specific attributes / selections that must be made?
I am not sure where the $TableName field needs to be placed or what type of field it should be - what should the formula be - if any?
How do I assign my specific @DbLookup to each column?
What are the specific naming conventions that I must follow?
In short - I am completely lost as to how to use the “<@>” tab of the table properties box. (Name/ID/Class/Other???)
I know this is probably very elementary to some of you guru’s but specific / detailed instructions would be greatly appreciated as I have yet to find them in Notes documentation or elsewhere on the web.
First of all - thanks for the responses so far. There are some points of clarity I need to offer up.
The user base of this system are not very advanced. I have to keep this as simple for the user as I can. Multiple tasks to print a doc would not be preferred. I need a single “Print” (just like everything else) to get this doc to print. This view basically needs to printed along with the document being printed.
I am using an embedded view (single category sort) to return the docs I want. I have a main doc and many many response docs. The response docs show up in the embedded view. These are the docs that ONLY pertain to the current open main doc. Then the user prints, they will want this view to print along with it.
I have read many people on here talking about the programmatic tables they have created but the exact details of how those tables are created has not been easy for me to find so I thought I would ask here. What I am asking for is details on how to use the ‘<@>’ tab of the tables properties and any other rules that would apply.
Thanks again for the responses.
I will look at attaching a ‘normal’ view and see where that goes. Exporting to excl I don’t think will be an option for me.
Sounds like you would really benefit from being able to export these documents into Excel and generating your reports that way.
Here’s an application that I put together that contains the components to do just that:
You’ll basically do this:
Define an Excel report “template” and attach said template to a “Report Template” document.
Create “metrics” (1st = Column A, 2nd = Column B, etc.) which are children documents of the “Report Template”, that will be used as formula evaluated against the reported document.
Define a target directory for this report.
All you need to do is pass it a NotesDocumentCollection and the Excel reporting engine takes over - drops your “report template” locally to your defined directory, iterates through all of the documents in your NDC, and evaluates each “metric” against each document, and uses that newly-formed content to populate your Excel “template”.
I typically create a few “report templates” and give the application users the ability to select the documents and the report type via a wizard of some sorts, but that’s the basic idea…