logo

New Response

« Return to the main article

You are replying to:

  1. I like some of the ideas, I use a few similar ones myself.

    A few other options people might want to consider...

    1. Using computed text and dbcolumns to retrieve computed HTML from documents and nest this inside passthru html tables on a form or page. As mentioned, computed values need to be recalculated if copy/paste. Just use a paste agent to solve that one.

    2. Create a view that shows the data as xml and treat this as an xml data island by using a lookup/dbcolumn etc... You can play around with the data, binding it to HTML tables and paging through the data for example.

    3. If you have lots of data you'll probably hit a text limit when a dbcolumn/lookup is used or you just might hit the maximun size of text/computed text for a document. In which case you can use a WebQueryOpen agent to write HTML to a computed RTF.

    4. The other idea I use sometimes is just using an agent to build a view like page, based on the results of a search or similar. Obviouslly there are possible performance issues when doing this, so take into account the size of the database, number of users etc...

    I like the Excel export idea, will be playing with this soon I should think! I have used the previous Excel export method Jake posted a few times now.

    Also, using CSS with views is a great idea, I use this frequently and not only is the download smaller, it's much easier to change the look of a whole load of views in one go by storing the CSS as a page or attachment (whatever takes your fancy)

Your Comments

Name:
E-mail:
(optional)
Website:
(optional)
Comment: