DAVID
|
| Posted: 02/05/2003, 5:34 AM |
|
Due to the fact that CCS is currently only dealing with templates (lang +
templates), I have encountered some limitations.
Consider a reporting page:
<SEARCH BLOCK>
<MIN DATE> <MAX DATE>
</SEARCH BLOCK>
<GRID BLOCK>
<DATE1>
<DATE2><DATE3><DATE4> -------------> <DATE N>
<VAR/CHARACTERISTIC 1>
<VAR/CHARACTERISTIC 2>
<VAR/CHARACTERISTIC 3>
<VAR/CHARACTERISTIC 4>
<VAR/PROPERTY 1>
<VAR/PROPERTY 2>
<VAR/PROPERTY 3>
<GRID BLOCK>
Without resorting to some client side scripting language ( i.e. javascript),
It seams impossible to generate a page that would flow in a horisontal
direction and be fixed in the verical direction. Ths very type of pages are
VERY common in statistical reports, where variable/characteristic/property
quantities are large.
|
|
|
 |
Shawn Mason
|
| Posted: 02/05/2003, 10:34 AM |
|
It seems those type of pages are more oriented towards a report and not an
entry page or grid. It is common practice on the web to use html grid, etc.
as reports when those types of pages have historically been reports and not
user interface screens. So, is it a limitation? Not if you look at the
purpose of CCS is to simplify creating the user interface aspects. It
really has no "true" reporting aspect (other then using the grid which like
you, is not really a great reporting methodolgy).
My recommendation is to use a reporting tool to do these types of pages.
--
Kindest Regards,
Shawn Mason,CCD,MCP
I.S. Software Design Associates
"DAVID" <codecharge_newsfeed@stridetech.com> wrote in message
news:b1r3tf$jq7$1@news.codecharge.com...
> Due to the fact that CCS is currently only dealing with templates (lang +
> templates), I have encountered some limitations.
> Consider a reporting page:
>
> <SEARCH BLOCK>
> <MIN DATE> <MAX DATE>
> </SEARCH BLOCK>
>
> <GRID BLOCK>
> <DATE1>
> <DATE2><DATE3><DATE4> -------------> <DATE N>
> <VAR/CHARACTERISTIC 1>
> <VAR/CHARACTERISTIC 2>
> <VAR/CHARACTERISTIC 3>
> <VAR/CHARACTERISTIC 4>
> <VAR/PROPERTY 1>
> <VAR/PROPERTY 2>
> <VAR/PROPERTY 3>
> <GRID BLOCK>
>
> Without resorting to some client side scripting language ( i.e.
javascript),
> It seams impossible to generate a page that would flow in a horisontal
> direction and be fixed in the verical direction. Ths very type of pages
are
> VERY common in statistical reports, where variable/characteristic/property
> quantities are large.
>
>
|
|
|
|
DAVID
|
| Posted: 02/05/2003, 1:25 PM |
|
That what I intend to do - to build a reporting tool. :)
For now, I am building a javascript array of result rows (via CCSLable ) and
then display it on the page/div/frame.
"Shawn Mason" <shawn@issda.com> wrote in message
news:b1rlfe$n72$1@news.codecharge.com...
> It seems those type of pages are more oriented towards a report and not an
> entry page or grid. It is common practice on the web to use html grid,
etc.
> as reports when those types of pages have historically been reports and
not
> user interface screens. So, is it a limitation? Not if you look at the
> purpose of CCS is to simplify creating the user interface aspects. It
> really has no "true" reporting aspect (other then using the grid which
like
> you, is not really a great reporting methodolgy).
>
> My recommendation is to use a reporting tool to do these types of pages.
>
>
> --
> Kindest Regards,
>
> Shawn Mason,CCD,MCP
> I.S. Software Design Associates
>
> "DAVID" <codecharge_newsfeed@stridetech.com> wrote in message
>news:b1r3tf$jq7$1@news.codecharge.com...
> > Due to the fact that CCS is currently only dealing with templates (lang
+
> > templates), I have encountered some limitations.
> > Consider a reporting page:
> >
> > <SEARCH BLOCK>
> > <MIN DATE> <MAX DATE>
> > </SEARCH BLOCK>
> >
> > <GRID BLOCK>
> > <DATE1>
> > <DATE2><DATE3><DATE4> -------------> <DATE N>
> > <VAR/CHARACTERISTIC 1>
> > <VAR/CHARACTERISTIC 2>
> > <VAR/CHARACTERISTIC 3>
> > <VAR/CHARACTERISTIC 4>
> > <VAR/PROPERTY 1>
> > <VAR/PROPERTY 2>
> > <VAR/PROPERTY 3>
> > <GRID BLOCK>
> >
> > Without resorting to some client side scripting language ( i.e.
> javascript),
> > It seams impossible to generate a page that would flow in a horisontal
> > direction and be fixed in the verical direction. Ths very type of pages
> are
> > VERY common in statistical reports, where
variable/characteristic/property
> > quantities are large.
> >
> >
>
>
|
|
|
|
Shawn Mason
|
| Posted: 02/06/2003, 7:17 AM |
|
Well, no disrespect intended, but why would you spend the time creating a
reporting tool when there are many of them out there. You have to consider
page breaks, browser support, possible printer support, OS support for with
various browser issues, etc? Most of the reporting tools out there cover
these details. Some decent in price (like Active Reports, VS View, etc.)
while others are quite ludicrous (Seagate Software's Crystal Reports
processor license cost of $25,000). There are also several other choices
especially in the java realm.
Just curious,
--
Kindest Regards,
Shawn Mason,CCD,MCP
I.S. Software Design Associates
"DAVID" <codecharge_newsfeed@stridetech.com> wrote in message
news:b1rvh1$bbl$1@news.codecharge.com...
> That what I intend to do - to build a reporting tool. :)
> For now, I am building a javascript array of result rows (via CCSLable )
and
> then display it on the page/div/frame.
>
>
>
>
>
> "Shawn Mason" <shawn@issda.com> wrote in message
>news:b1rlfe$n72$1@news.codecharge.com...
> > It seems those type of pages are more oriented towards a report and not
an
> > entry page or grid. It is common practice on the web to use html grid,
> etc.
> > as reports when those types of pages have historically been reports and
> not
> > user interface screens. So, is it a limitation? Not if you look at the
> > purpose of CCS is to simplify creating the user interface aspects. It
> > really has no "true" reporting aspect (other then using the grid which
> like
> > you, is not really a great reporting methodolgy).
> >
> > My recommendation is to use a reporting tool to do these types of pages.
> >
> >
> > --
> > Kindest Regards,
> >
> > Shawn Mason,CCD,MCP
> > I.S. Software Design Associates
> >
> > "DAVID" <codecharge_newsfeed@stridetech.com> wrote in message
> >news:b1r3tf$jq7$1@news.codecharge.com...
> > > Due to the fact that CCS is currently only dealing with templates
(lang
> +
> > > templates), I have encountered some limitations.
> > > Consider a reporting page:
> > >
> > > <SEARCH BLOCK>
> > > <MIN DATE> <MAX DATE>
> > > </SEARCH BLOCK>
> > >
> > > <GRID BLOCK>
> > > <DATE1>
> > > <DATE2><DATE3><DATE4> -------------> <DATE N>
> > > <VAR/CHARACTERISTIC 1>
> > > <VAR/CHARACTERISTIC 2>
> > > <VAR/CHARACTERISTIC 3>
> > > <VAR/CHARACTERISTIC 4>
> > > <VAR/PROPERTY 1>
> > > <VAR/PROPERTY 2>
> > > <VAR/PROPERTY 3>
> > > <GRID BLOCK>
> > >
> > > Without resorting to some client side scripting language ( i.e.
> > javascript),
> > > It seams impossible to generate a page that would flow in a horisontal
> > > direction and be fixed in the verical direction. Ths very type of
pages
> > are
> > > VERY common in statistical reports, where
> variable/characteristic/property
> > > quantities are large.
> > >
> > >
> >
> >
>
>
|
|
|
|
Daniel Gaudreault
|
| Posted: 02/06/2003, 10:22 AM |
|
There is also the free "Agata Report" engine that run via php-gtk. It is a
Crystal Reports clone.
http://agata.codigolivre.org.br/
Best Regard,
Danie Gaudreault
"Shawn Mason" <shawn@issda.com> wrote in message
news:b1tu9q$2bt$1@news.codecharge.com...
> Well, no disrespect intended, but why would you spend the time creating a
> reporting tool when there are many of them out there. You have to
consider
> page breaks, browser support, possible printer support, OS support for
with
> various browser issues, etc? Most of the reporting tools out there cover
> these details. Some decent in price (like Active Reports, VS View, etc.)
> while others are quite ludicrous (Seagate Software's Crystal Reports
> processor license cost of $25,000). There are also several other choices
> especially in the java realm.
>
> Just curious,
>
> --
> Kindest Regards,
>
> Shawn Mason,CCD,MCP
> I.S. Software Design Associates
>
> "DAVID" <codecharge_newsfeed@stridetech.com> wrote in message
>news:b1rvh1$bbl$1@news.codecharge.com...
> > That what I intend to do - to build a reporting tool. :)
> > For now, I am building a javascript array of result rows (via CCSLable )
> and
> > then display it on the page/div/frame.
> >
> >
> >
> >
> >
> > "Shawn Mason" <shawn@issda.com> wrote in message
> >news:b1rlfe$n72$1@news.codecharge.com...
> > > It seems those type of pages are more oriented towards a report and
not
> an
> > > entry page or grid. It is common practice on the web to use html
grid,
> > etc.
> > > as reports when those types of pages have historically been reports
and
> > not
> > > user interface screens. So, is it a limitation? Not if you look at
the
> > > purpose of CCS is to simplify creating the user interface aspects. It
> > > really has no "true" reporting aspect (other then using the grid which
> > like
> > > you, is not really a great reporting methodolgy).
> > >
> > > My recommendation is to use a reporting tool to do these types of
pages.
> > >
> > >
> > > --
> > > Kindest Regards,
> > >
> > > Shawn Mason,CCD,MCP
> > > I.S. Software Design Associates
> > >
> > > "DAVID" <codecharge_newsfeed@stridetech.com> wrote in message
> > >news:b1r3tf$jq7$1@news.codecharge.com...
> > > > Due to the fact that CCS is currently only dealing with templates
> (lang
> > +
> > > > templates), I have encountered some limitations.
> > > > Consider a reporting page:
> > > >
> > > > <SEARCH BLOCK>
> > > > <MIN DATE> <MAX DATE>
> > > > </SEARCH BLOCK>
> > > >
> > > > <GRID BLOCK>
> > > > <DATE1>
> > > > <DATE2><DATE3><DATE4> -------------> <DATE N>
> > > > <VAR/CHARACTERISTIC 1>
> > > > <VAR/CHARACTERISTIC 2>
> > > > <VAR/CHARACTERISTIC 3>
> > > > <VAR/CHARACTERISTIC 4>
> > > > <VAR/PROPERTY 1>
> > > > <VAR/PROPERTY 2>
> > > > <VAR/PROPERTY 3>
> > > > <GRID BLOCK>
> > > >
> > > > Without resorting to some client side scripting language ( i.e.
> > > javascript),
> > > > It seams impossible to generate a page that would flow in a
horisontal
> > > > direction and be fixed in the verical direction. Ths very type of
> pages
> > > are
> > > > VERY common in statistical reports, where
> > variable/characteristic/property
> > > > quantities are large.
> > > >
> > > >
> > >
> > >
> >
> >
>
>
|
|
|
|
DAVID
|
| Posted: 02/06/2003, 10:50 AM |
|
Don't you guys think it would be extremely cool to have statistics and
reports built in the same framework as the rest of the site? Having the same
authentication / authorization applied to the reporting areas as well as
data entry? We are not talking about a complex, generic query engine here -
it's just a set of less then 100 predefined , but searchable reports.
To add my 10 cents into the bucket - why use codecharge, if I can do the
same in mod_perl? CCS Pages are HEAVY, framework is flooded with unnecessary
bagage (i.e. CCSLookup and alike).
Take a look at this example site:
http://staging.stridetech.com/flane/index.cgi . It is running on 98% pure
CCS genned code.
Now compare it to www.yahoo.com or better www.myway.com .
The answer is simple - CCS generates code you never even bother looking
into. Even though pages do not perform well, it is very easy to add a few of
them in under 10 minutes. For lightly accessed areas, like reporting this
should not be a problem. For sites with one visitor a day it should not be a
problem either. Say CCS Team included some banner support into their portal
example. What if you want the admin of the site to see statistics for the
banner usage, and affiliate referrals? Do you really want to write the 1% of
your site in some other framework? Don't take me wrong - I have an image
upload/verification/auto resize tool. I HAD to come up with it because CCS
just does not support this kind of crap. It just occurs to me that
collecting bits and pieces into something usefull is sometimes not a good
idea.
"Daniel Gaudreault" <danielg@cadlink.com> wrote in message
news:b1u953$o23$1@news.codecharge.com...
> There is also the free "Agata Report" engine that run via php-gtk. It is
a
> Crystal Reports clone.
>
> http://agata.codigolivre.org.br/
>
> Best Regard,
>
> Danie Gaudreault
>
>
> "Shawn Mason" <shawn@issda.com> wrote in message
>news:b1tu9q$2bt$1@news.codecharge.com...
> > Well, no disrespect intended, but why would you spend the time creating
a
> > reporting tool when there are many of them out there. You have to
> consider
> > page breaks, browser support, possible printer support, OS support for
> with
> > various browser issues, etc? Most of the reporting tools out there
cover
> > these details. Some decent in price (like Active Reports, VS View,
etc.)
> > while others are quite ludicrous (Seagate Software's Crystal Reports
> > processor license cost of $25,000). There are also several other
choices
> > especially in the java realm.
> >
> > Just curious,
> >
> > --
> > Kindest Regards,
> >
> > Shawn Mason,CCD,MCP
> > I.S. Software Design Associates
> >
> > "DAVID" <codecharge_newsfeed@stridetech.com> wrote in message
> >news:b1rvh1$bbl$1@news.codecharge.com...
> > > That what I intend to do - to build a reporting tool. :)
> > > For now, I am building a javascript array of result rows (via
CCSLable )
> > and
> > > then display it on the page/div/frame.
> > >
> > >
> > >
> > >
> > >
> > > "Shawn Mason" <shawn@issda.com> wrote in message
> > >news:b1rlfe$n72$1@news.codecharge.com...
> > > > It seems those type of pages are more oriented towards a report and
> not
> > an
> > > > entry page or grid. It is common practice on the web to use html
> grid,
> > > etc.
> > > > as reports when those types of pages have historically been reports
> and
> > > not
> > > > user interface screens. So, is it a limitation? Not if you look at
> the
> > > > purpose of CCS is to simplify creating the user interface aspects.
It
> > > > really has no "true" reporting aspect (other then using the grid
which
> > > like
> > > > you, is not really a great reporting methodolgy).
> > > >
> > > > My recommendation is to use a reporting tool to do these types of
> pages.
> > > >
> > > >
> > > > --
> > > > Kindest Regards,
> > > >
> > > > Shawn Mason,CCD,MCP
> > > > I.S. Software Design Associates
> > > >
> > > > "DAVID" <codecharge_newsfeed@stridetech.com> wrote in message
> > > >news:b1r3tf$jq7$1@news.codecharge.com...
> > > > > Due to the fact that CCS is currently only dealing with templates
> > (lang
> > > +
> > > > > templates), I have encountered some limitations.
> > > > > Consider a reporting page:
> > > > >
> > > > > <SEARCH BLOCK>
> > > > > <MIN DATE> <MAX DATE>
> > > > > </SEARCH BLOCK>
> > > > >
> > > > > <GRID BLOCK>
> > > > > <DATE1>
> > > > > <DATE2><DATE3><DATE4> -------------> <DATE N>
> > > > > <VAR/CHARACTERISTIC 1>
> > > > > <VAR/CHARACTERISTIC 2>
> > > > > <VAR/CHARACTERISTIC 3>
> > > > > <VAR/CHARACTERISTIC 4>
> > > > > <VAR/PROPERTY 1>
> > > > > <VAR/PROPERTY 2>
> > > > > <VAR/PROPERTY 3>
> > > > > <GRID BLOCK>
> > > > >
> > > > > Without resorting to some client side scripting language ( i.e.
> > > > javascript),
> > > > > It seams impossible to generate a page that would flow in a
> horisontal
> > > > > direction and be fixed in the verical direction. Ths very type of
> > pages
> > > > are
> > > > > VERY common in statistical reports, where
> > > variable/characteristic/property
> > > > > quantities are large.
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
|
|
|
|
Kasper Pedersen
|
| Posted: 02/07/2003, 6:33 AM |
|
Step 1: Choose "Columnar layout"
Step 2: Change template like this (remove any TABLE tags)
------------------------------------
<!-- BEGIN Grid gruppe -->
<TABLE><TR>
<!-- BEGIN Row -->
<TD>
<table>
......... NORMAL GRID CELLS ............
</table>
</TD>
<!-- END Row -->
</TR></TABLE>
....
------------------------------------
Step 3: Remove "headers" and adjust cell heights in order to make the design
consistent
Best regards
Kasper
"DAVID" <codecharge_newsfeed@stridetech.com> wrote in message
news:b1r3tf$jq7$1@news.codecharge.com...
> Due to the fact that CCS is currently only dealing with templates (lang +
> templates), I have encountered some limitations.
> Consider a reporting page:
>
> <SEARCH BLOCK>
> <MIN DATE> <MAX DATE>
> </SEARCH BLOCK>
>
> <GRID BLOCK>
> <DATE1>
> <DATE2><DATE3><DATE4> -------------> <DATE N>
> <VAR/CHARACTERISTIC 1>
> <VAR/CHARACTERISTIC 2>
> <VAR/CHARACTERISTIC 3>
> <VAR/CHARACTERISTIC 4>
> <VAR/PROPERTY 1>
> <VAR/PROPERTY 2>
> <VAR/PROPERTY 3>
> <GRID BLOCK>
>
> Without resorting to some client side scripting language ( i.e.
javascript),
> It seams impossible to generate a page that would flow in a horisontal
> direction and be fixed in the verical direction. Ths very type of pages
are
> VERY common in statistical reports, where variable/characteristic/property
> quantities are large.
>
>
|
|
|
|
DAVID
|
| Posted: 02/12/2003, 6:09 AM |
|
90% agree.
There are still some problems with this solution:
i.e. one must use "nowrap" on all td's in order for proper cell alignmet to
take place.
Also, page navigator must be taken out, and aligned elsewhere.
Once I get a somewhat functional template I'll make sure to post it here.
"Kasper Pedersen" <kasper@bentbyg.dk> wrote in message
news:b20g3u$da7$1@news.codecharge.com...
> Step 1: Choose "Columnar layout"
>
> Step 2: Change template like this (remove any TABLE tags)
> ------------------------------------
>
> <!-- BEGIN Grid gruppe -->
> <TABLE><TR>
>
> <!-- BEGIN Row -->
> <TD>
>
> <table>
>
> ........ NORMAL GRID CELLS ............
>
> </table>
>
> </TD>
> <!-- END Row -->
>
> </TR></TABLE>
> ...
>
> ------------------------------------
>
> Step 3: Remove "headers" and adjust cell heights in order to make the
design
> consistent
>
> Best regards
> Kasper
>
> "DAVID" <codecharge_newsfeed@stridetech.com> wrote in message
>news:b1r3tf$jq7$1@news.codecharge.com...
> > Due to the fact that CCS is currently only dealing with templates (lang
+
> > templates), I have encountered some limitations.
> > Consider a reporting page:
> >
> > <SEARCH BLOCK>
> > <MIN DATE> <MAX DATE>
> > </SEARCH BLOCK>
> >
> > <GRID BLOCK>
> > <DATE1>
> > <DATE2><DATE3><DATE4> -------------> <DATE N>
> > <VAR/CHARACTERISTIC 1>
> > <VAR/CHARACTERISTIC 2>
> > <VAR/CHARACTERISTIC 3>
> > <VAR/CHARACTERISTIC 4>
> > <VAR/PROPERTY 1>
> > <VAR/PROPERTY 2>
> > <VAR/PROPERTY 3>
> > <GRID BLOCK>
> >
> > Without resorting to some client side scripting language ( i.e.
> javascript),
> > It seams impossible to generate a page that would flow in a horisontal
> > direction and be fixed in the verical direction. Ths very type of pages
> are
> > VERY common in statistical reports, where
variable/characteristic/property
> > quantities are large.
> >
> >
>
>
|
|
|
|
DAVID
|
| Posted: 02/12/2003, 7:00 AM |
|
Ok, I followed your guidelines. This does work out pretty well. Also,
consider the "Creating a Report-like Grid" article (found at
http://support.codecharge.com/kb_article.asp?kb_article...3&article_id=57
). If the table has some kind of grouping field as well,
with page navigation,records per page and max records disabled, I think I
could come up with report by groupping element.
To run this template create a table with
a. date field (primary key) and connect closing_dt to it .
b. two integer fields and connect n_users , i_users
c. two float fields and connect tot_revenue ,avg_revenue respectivelly
--
d. populate random values, try to make dates sequential.
The template I came up with is between the cut lines:
-------------------------------CUT----------------------------------------
<html>
<head>
<title>Test Report</title>
<link rel="stylesheet" type="text/css"
href="Themes/Multipads/Style.css"></head>
<body bgcolor="#FFFFFF" text="#000000" link="#800000" vlink="#800000">
<!-- BEGIN Record ilead_revenue_bSearch -->
<form method="post" action="{Action}" name="ilead_revenue_bSearch">
<font class="MultipadsFormHeaderFont">To narrow the report to specific
date range you may choose lower and/or upper limits for the range</font>
<table cellpadding="2" cellspacing="2" class="MultipadsFormTABLE">
<!-- BEGIN Error -->
<tr>
<td colspan="2" class="MultipadsDataTD">{Error}</td>
</tr>
<!-- END Error -->
<tr>
<td nowrap class="MultipadsFieldCaptionTD">MIN DATE </td>
<td nowrap class="MultipadsFieldCaptionTD">MAX DATE </td>
</tr>
<tr>
<td class="MultipadsDataTD"><input type="text" name="s_CLOSING_DT_min"
value="{s_CLOSING_DT_min}" maxlength="10" size="10"
class="MultipadsInput"> </td>
<td class="MultipadsDataTD"><input type="text" name="s_CLOSING_DT_max"
value="{s_CLOSING_DT_max}" maxlength="10" size="10"
class="MultipadsInput"> </td>
</tr>
<tr>
<td colspan="2" align="right" nowrap class="MultipadsFooterTD">
<!-- BEGIN Button DoSearch --><input name="DoSearch" type="submit"
value="Search" class="MultipadsButton"><!-- END Button
DoSearch --> </td>
</tr>
</table>
</form>
<!-- END Record ilead_revenue_bSearch -->
<!-- BEGIN Grid ilead_revenue_b -->
<table bordercolor=red border=4>
<tr>
<td>
<table border="4" bordercolor=green class="MultipadsFormTABLE" width=0%>
<tr>
<td>
<table cellpadding="0" cellspacing="0" class="MultipadsFormTABLE">
<tr>
<td nowrap class="MultipadsColumnTD">CLOSING DT </td>
</tr>
<tr>
<td nowrap class="MultipadsColumnTD">NEW USERS </td>
</tr>
<tr>
<td nowrap class="MultipadsColumnTD">ILEAD USERS </td>
</tr>
<tr>
<td nowrap class="MultipadsColumnTD">TOTAL REVENUE </td>
</tr>
<tr>
<td nowrap class="MultipadsColumnTD">AVERAGE REVENUE </td>
</tr>
</table>
</td>
<!-- BEGIN Row -->
<td>
<table cellpadding="0" cellspacing="0" class="MultipadsFormTABLE">
<tr>
<td class="MultipadsDataTD">{CLOSING_DT} </td>
</tr>
<tr>
<td class="MultipadsDataTD">{N_USERS} </td>
</tr>
<tr>
<td class="MultipadsDataTD">{I_USERS} </td>
</tr>
<tr>
<td class="MultipadsDataTD">{TOT_REVENUE} </td>
</tr>
<tr>
<td class="MultipadsDataTD">{AVG_REVENUE} </td>
</tr>
</table>
</td>
<!-- END Row -->
<!-- BEGIN NoRecords -->
<td class="MultipadsDataTD">No records </td>
<!-- END NoRecords -->
</tr>
</td>
</tr>
</tr>
</td>
<table bordercolor=blue border=4 width="100%">
<tr>
<td nowrap class="MultipadsFooterTD">
<!-- BEGIN Navigator Navigator -->
<!-- BEGIN First_On --><a href="{First_URL}"
class="MultipadsNavigatorLink">First</a><!-- END First_On -->
<!-- BEGIN First_Off -->First<!-- END First_Off -->
<!-- BEGIN Prev_On --><a href="{Prev_URL}"
class="MultipadsNavigatorLink">Prev</a><!-- END Prev_On -->
<!-- BEGIN Prev_Off -->Prev<!-- END Prev_Off -->
<!-- BEGIN Pages -->
<!-- BEGIN Page_On --><a href="{Page_URL}"
class="MultipadsNavigatorLink">{Page_Number}</a> <!-- END Page_On -->
<!-- BEGIN Page_Off -->{Page_Number} <!-- END Page_Off --><!--
END Pages -->of
{Total_Pages}
<!-- BEGIN Next_On --><a href="{Next_URL}"
class="MultipadsNavigatorLink">Next</a><!-- END Next_On -->
<!-- BEGIN Next_Off -->Next<!-- END Next_Off -->
<!-- BEGIN Last_On --><a href="{Last_URL}"
class="MultipadsNavigatorLink">Last</a><!-- END Last_On -->
<!-- BEGIN Last_Off -->Last<!-- END Last_Off --><!-- END Navigator
Navigator -->
</td>
</tr>
</table>
</td><tr>
</table>
<!-- END Grid ilead_revenue_b -->
</body>
</html>
-------------------------------CUT----------------------------------------
|
|
|
|
|
