Clickable email link in apex report

Hi,
I have emails information store in a table, and would like to make this email clickable.
Is this possible? How?
I was able to do this in forms, but, don't know how this maybe done on the classic reports/interactive reports.
Thank you for your help!
LC

LC,
This code fires as a URL link from a report, report attributes are wrapped in *#* symbols, line feeds are *%0A%0A*
mailto:#EMAIL#?subject=Renewal Insurance Certificate for the State of New Hampshire&cc=#EMAIL_ADDR#&Body=Dear #FIRSTNAME#,%0A%0AOur records show that when #VENDOR_NAME# and the State of New Hampshire concluded their contract for #DSC#, the proof of insurance certificate you submitted had an expiration date of, #INACTIVE_DT#. Please submit a renewal certificate to me at the at the address below and I will update your records. %0A%0ABest RegardsJeff

Similar Messages

Column Links in Apex Reports

I am using version 4.0 of APEX. My question concerns linking to other APEX pages from a report. In APEX we link to another page, which may be a form or another report, by using a column in the report as a link column. Any column may be used to transfer values from any other column. This works fine, but the disadvantage is that whichever column is used as the link column has a heading which identifies the column's purpose but may not identify the purpose of the transition to another page. In Oracle Forms, we could use buttons as a column of the multi-row screen (i.e. same as APEX report), and the button's label identified the purpose for the transition.
Is there any way to create a column in an APEX report to serve the same purpose as the button in Oracle Forms?

Doug wrote:
I am using version 4.0 of APEX. My question concerns linking to other APEX pages from a report. In APEX we link to another page, which may be a form or another report, by using a column in the report as a link column. Any column may be used to transfer values from any other column. This works fine, but the disadvantage is that whichever column is used as the link column has a heading which identifies the column's purpose but may not identify the purpose of the transition to another page. In Oracle Forms, we could use buttons as a column of the multi-row screen (i.e. same as APEX report), and the button's label identified the purpose for the transition.
Is there any way to create a column in an APEX report to serve the same purpose as the button in Oracle Forms?
When discussing "reports" it is essential to indicate whether this means a standard report or an interactive report in order to receive an appropriate response.
It is possible to create a link column that is distinct from report data columns. In standard reports, this is done using the Add Column Link option from the Tasks menu in the right sidebar of the Report Attributes page. In interactive reports, define a Link Column on the Report Attributes page.
To provide further information about links to users in both cases, specify an HTML title attribute for the link in the Link Attributes property of the link definition. This will be rendered as a tooltip when the cursor hovers over the link in visual browsers, and as an audio cue on navigation to the link when using a screen reader.

BLOB content download link on apex report

Hi Guys,
I have a simple form where user can attach file and save the records. I iterate through wwv_flow_files and get the file and save it to a custom table which has BLOB column. On another report page i display uploaded file details. What i need is, there must be a column with download link when user clink the link appropriate file should be downloaded. How can i do this ?
Really appreciate if someone can assist me on this.
Thanks Guys.

See About BLOB Support in Forms and Reports.
There's an OBE tutorial that followed the introduction of declarative BLOB support in 3.1 as well. (An earlier version but it is still relevant to APEX 4.x.)
(Please make an effort to consult the documentation and thoroughly search the forum for previous coverage of a topic. This is a much discussed question.)

Sending Unique email links from APEX

Hello folks,
I wonder if i can create a email form that can allow the users to choose the Recipients address from the DB ( I have a table with the email addresses) & to send them a link for a Survey application, BUT my idea is to use a parameter for the email address with the link ....so once the recipients receive the link they will be allowed to Submit the survey ONLY ONCE by checking the parameter value?!!
Regards,
Ehammad

Hi every1,
Thanx all for your reply,
My idea was about sending the survey link for my customers by email..once they click & submitted responds it will Not allow him to use the link again..even if he forwarded to another email, to prevent the customer from submitting the survey more than once by using different emails address!!...
I Dunno if this idea is logical or poor ...i need ur advices all..
I customers are login through "PUBLIC_USER" ...
- Yes its logic to generate Unique ID , but my table is already have my Transaction Unique ID ,and still the user can use the link again to submit the results because he use "PUBLIC_USER" on login.
-I am using the email address column in the transaction table to check if the user had already submitted the survey or no, but am not using a field in the survey to ask for the user email address, if i did, still the user can use more than one email to submit the survey.
-I will check the SYS_GUID. Can I add this generated Key to the Application link?! so each user can get the link like this
ex " APEX application Link+ SYS_GUID key"?!! instant of using the email parameter?
Please advice if am missing somthing or my idea is not logic...
Regards,
ehammad

How to change port 8080 to another and change email link

HI ,
We can log onto Business Objects fine both in infoview and CMC using the URL http://servername:8080 but when we run a report and email the link to users the embedded URL http://servername:8080" does not work as it is blocked by our ISA. As a result we need to change the port from 8080 to another. We have changed the port as directed by this link:- http://www.forumtopics.com/busobj/viewtopic.php?p=284295&sid=630c45ef6866f91e81813104372c64e5 and when we change the infoview and CMC URLs they work fine on the new port. However the email link to the report still goes out with port 8080 - what do i need to change in order to get the email to see the new port and hence allow our users to be able to access reports via the link we distribute.
thanks
Chris

Hi,
the URL syntax shows that you are using BO XI 3.x. I assume that you add %SI_VIEWER_URL% in the message body of your email when you schedule the report.
Please go to the CMC and select Applications. Select the CMC entry and press the right mouse button to invoke the context menu. Select the processing settings entry and modify the port in the URL you are seeing there.
Regards,
Stratos

Email links in an interactive report

Hi
Is it possible to have email links in an interactive report?
i.e display something like "[email protected]" as a clickable link that invokes the default external email program with the "To:" field populated?
Thanks!

Another nifty way to do it, while saving precious screen space would be:
'<a href="mailto:' || email || "><img src="/i/pkt_mailto.gif" title="' || email || '"></a>' "E-mail"
email being the name of the column that contains the E-mail address. It will display like a small envelope with an e-mail displayed as you hover over it.
Vojin

Interactive report conditional display of link column - apex 4

I create an interactive report
select object_id,
       object_name,
       case
        when mod(rownum, 2) = 0
        then 'block'
        else 'none'
       end display_link
from user_objects
where rownum <= 10in the Link Column for the report I selected one of the edit icons and put the following in the link attributes
style="display:#DISPLAY_LINK#"I also edited the object_id and set the Column Link and selected an edit icon and put the same style in the link attributes.
The link under the column displays correctly but the link for the report does not seem to substitute the #DISPLAY_LINK# from the report. Any Ideas?

Here's how I've done this:
SELECT ORG_ID,
       CLEARER_NAME,
       LEGAL_NAME,
       MARGINING_ACCOUNT,
       RULE_GROUP_DESCR,
       VIOLATION_COLOR,
       VIOLATION_LEVEL,
       CASE MARGIN_IND
        WHEN 'Y' THEN '&nbsp'
        ELSE '<a href="#" title="Ignore This Alert"><img src="/i/ice/images/hide.png" alt="Ignore"></a>'
       END AS IGNORE_LINK,
       ....This takes care of either showing (or not showing) the link.
IN order to process when it is present, not that the address is "#" This will cause your cursor to change to a hand (or whatever your pointer is) when the mouse floats over the link. The actual transfer to the next page, I handle with jQuery/JavaScript.
Create a Dynamic Action.
Event: Click
Selector Type: jQuery Selector
jQuery Selector: 'aalt'
Event Scope: Live
(note that the jQuery Selector is finding the alt attribute that I set on my link in the SELECT above . Tweak as needed.
This "Action" for this DA will be to "execute JavaScript code"
Normally, I would set some values into Page Items and then create a branch to pass this values to the next page. I am doing the same thing in the following code. I am getting the values off of the row wherein the user clicked on the link. I am setting these values from the row into the page item values. Then, I am submitting the page. All the "htmldb_Get" business is just stuff that I have to do to get the page item values into the session (so that I can pass them to the next page).
var clickedRow = this.triggeringElement.parentNode.parentNode.parentNode;
var ruleGroupDescr = $(clickedRow).children('td[headers="RULE_GROUP_DESCR"]').html();
var ajaxRequest = new htmldb_Get(null, $x('pFlowId').value, null, 0);
gReturn = ajaxRequest.get();
$s('P31_RULE_GROUP_DESCR', ruleGroupDescr );
ajaxRequest = null;
var clearerName = $(clickedRow).children('td[headers="CLEARER_NAME"]').html();
var ajaxRequest = new htmldb_Get(null, $x('pFlowId').value, null, 0);
gReturn = ajaxRequest.get();
$s('P31_CLEARER_NAME', clearerName );
ajaxRequest = null;
apex.submit("IGNORE");Finally, just create a branch to the next page and set the items on the next page to the ones on this page that are being set in the above script. Note that in my example, I have set the request to "Ignore" when I submitted; so, I set the condition of my branch to be Request = IGNORE.
Hope this helps,
-Joe

URGENT Printing a BI publisher report from a column link in APEX

I am developing an APEX report with a column link that will call a BI publisher report, the case is the link column in the APEX report will pass the item number to the BI publisher query.
At the moment this is what I am doing:
1- Create a hidden item on top of page zero. (e.g. PARAM1_VALUE)
2- Create a report query and a report layout (For BI Publisher) in the Shared Components. (e.g ITEM_REPORT)
3- Include the state session in the report query and reference that item in the query. (e.g. SELECT * FROM items where item_number = :PARAM1_VALUE)
4- Create an APEX report displaying orders with the item number as a link column.
5- In the Link column I set the report URL request to be "PRINT_SERVER=ITEM_REPORT".
6- In addition I set the PARAM1_VALUE to be #ITEM_NUMBER# on the link.
When I press on the link the BI publisher report prints but it doesn't display anything except the Headers, my understanding is that PARAM1_VALUE is not set with the item_number value when I press on the link and thus the query returns no results as when I remove the condition from the query i can see the report printing.
Please help as this is urgent

I opened the session and it is there with a proper value, it appears that whenever I enable the inclusion of session state in my shared components query the query returns no rows even if I am not using the item in the query.
So if my query is "SELECT * FROM items" it will display nothing, the only way to get the report data back is to untick the inclusion of the session state and remove any reference to the item from my query, then I will get the report with all my data (which is NOT what I am trying to do).
Thanks alot
Khaled Jamoos

Re: Problem providing download link for BLOB data in apex report

Hi Don,
Your solution below worked but in the download option i only see save but not open for PDf file in the blob. Please let me know if you have any suggestion to achieve it
Thanks
Jo
Problem providing download link for BLOB data in apex report
591953 Nov 19, 2008 1:55 PM (in response to 660436)
Currently Being Moderated
Good morning,
Here is how I have solved this problem.
1. The select statement in the sql for the report should not include the BLOB column. I decided to select only 2 columns, the column that has the key and the column with the filename.
2. On the first column ( the primary key ) I put in the format statement that was simply DOWNLOAD:TABLENAME:BLOB_COLUMN:PRIMARY_KEY
This works. I believe that the Oracle error I was getting was because I was trying to apply this format statement to the actual BLOB column.
So, it appears that you can use any of the columns in the report to hold the DOWNLOAD format statement since in the format statement, you are defining the BLOB table, BLOB column and the primary key into that column.
Hope this helps,
Don.

Branched out from a years old thread.
user3003326 Don't post to old threads, please.

Calling a .rdf report from a link on a apex report column

Hi,
I want to call a xxx.rdf report from a link on a apex report column.
Can anyone help me on this ?
Best regards,
JCN

Hi,
Sorry - I should have read a bit further in your last post!
The url variable that you're defining should just be the URL string that you want to create, so you only need the "http://........" part. There's also a + missing after the "&TODT..." string.
The "DEA_PERMIT_ID=&G_PERMIT_ID." part at the end should have an & at the start to indicate a new parameter in the URL. Otherwise, &G_PERMIT_ID. would be replaced by the value stored in the session for the G_PERMIT_ID item (presumably that is an Application Item?).
So:
function callPopup()
var url = "'http://snapper.accsp.org/reports/rwservlet?destype=cache&desformat=PDF&report=edr_landings_dollars_by_vessel.rdf&userid=evtr_report/chicken99@safis&FROMDT=" + $v("P810_FROM") + "&TODT=" + $v("P810_TO") + "&DEA_PERMIT_ID=&G_PERMIT_ID.";
popupURL(url);
}Andy

DB links, Bind variables & APEX reports performance

Hello,
So the problem is simply that I have two databases:
A : Has table T1
B : (APEX database)
I have an APEX report that simply does the following
Select col1, col2.. from A@dblink
This is abviously straighforward, however, I start having considrable performance issues if I have any filters applied to this query using APEX items ( bind variables) :
Select col1, col2.. from T1@dblink_A_B
where col1 > :PX_item
I ran the explain plan and noticed that using the bind variables forces the query to be done on database B, not A which is causing the performance issues.
I am sure that many of you ran into this issue before, but does anyone know how to resolve this issue ? I am thinking about using Pipelined functions, but am not sure if that will work well if I have a lot of records returned by the query or if this will resolve the issue at all.... your thoughts are appreciated..
Thanks,
Sam

I've always been able to work around my DB link issues in Apex. As suggested, driving_site hint should be tried. Oracle documentation on it isn't great, but I follow this:
- don't bother including other hints together with driving_site, as they get stripped out when your sql is passed to the remote DB (as per driving_site hint).
- if you have have subqueries - specifiy driving_site hint in that section of the SQL too. I don't have any proof that this is really required - but it doesnt hurt.
- include driving_site hint even if all tables are remote. Careful of refs to pseudo cols like sysdate, user etc. I think they are taken as local refs - not remote. I havent tested this properly to confirm.
- dumb down your test case to eliminate refs to sysdate, subqueries etc.
- remember that items are text, so you'd need to do to_number(), to_date() on them where appropriate on them in your SQL at the least.
Seeing as you control the content of your items, SQL injection is a reduced risk. Assuming that's not your top concern anyway, don't get carried away with the bind-variable vs literals debate. Apex does lots of nasty inefficient stuff like IR searches. I'd never use an IR in something that really needs to be scalable anyway. Soo... construct SQL with littlerals based on your items (assuming item refs are the cause of your issue).
region type=SQL Query (PL/SQL function body returning SQL query)
begin
return 'SELECT /*+ DRIVING_SITE(a) */ a.empno,a.ename,a.job,a.mgr,a.loc
        FROM emp@MY_DBLNK A
       WHERE a.empno = '||:P123_EMPNO||'
       ORDER BY 1,2,3';
end;Assuming your queries are expensive to execute (local or remote) and dont return too many records (else collection table can get really big), then caching the resultset in a collection gives you nice fast pagination, when using a PPR report. Keep a watch on the size of the collection table - truncate it manually if you accidentally populate it with a big cartesean product etc, else performance could degrade.
Do main query to populate collection before header. PPR pagination doesnt reload the page, so before-header process only runs once. In my case it works like:
-- reload button to re-load page, to force a query re-run. The html_Submit_Progress thing loads an 'busy processing' image.
<input type="button" value="Run query" onclick="javascript:this.disabled=true;this.value='Running...';html_Submit_Progress(this);" id="SUBMIT" />
-- On Load - before header process to populate collection (call in a regular region to see errors, until ironed out)
declare
q varchar2(4000);
v_t0   PLS_INTEGER := DBMS_UTILITY.get_time;
begin
   :P0_QSEC := '0';
IF APEX_COLLECTION.COLLECTION_EXISTS(P_COLLECTION_NAME=> 'Q1')
THEN
    APEX_COLLECTION.DELETE_COLLECTION(P_COLLECTION_NAME=>'Q1');
END IF;
if (:P0_DBLNK is not null) then
    q:= 'SELECT /*+ DRIVING_SITE(a) */ a.empno,a.ename,a.job,a.mgr,a.loc
        FROM emp@'||:P0_DBLNK||' a
       WHERE a.job like "M%"
        AND a.empno = #EMPNO#
       ORDER BY 1,2,3';
    q:= replace(q, '"', '''');
    q:= replace(q, '#EMPNO#', :P123_EMPNO);
    -- bulk
    APEX_COLLECTION.CREATE_COLLECTION_FROM_QUERY_B(
        P_COLLECTION_NAME => 'Q1',
        P_QUERY => Q);
   -- record count
   -- APEX_COLLECTION.collection_member_count
end if;
-- display in page footer or whatever
:P0_QSEC := TO_CHAR ((DBMS_UTILITY.get_time - v_t0) / 100, '000.00') || ' sec';
exception
when others then
raise_application_error(-20501, :P0_DBLNK||'< br >'||sqlerrm||'< br >'||q );
end;
-- then PPR report is just like
Select C001, C002, C003, C004, C005
From apex_collections
Where collection_name = 'Q1'
order by seq_id;Edited by: maceyah on Sep 7, 2011 9:26 AM
Useful link on bind variables for CREATE_COLLECTION_FROM_QUERY_B ==> https://forums.oracle.com/forums/thread.jspa?threadID=2305634&tstart=0
Edited by: maceyah on Mar 2, 2012 3:18 PM

Email link to open oracle apex

Hi all expert,
Currently, my application is running in apex 4.1 oracle db 11g XE.
How can i open oracle apex page from outside link?
My program follow is in this way, DBMS_JOB will call a procedure to send email to user when there is a new records to user.
The email contain a link (eg: "http://172.23.8.11:8080/apex/f?p=100:20101:::::P20101_TNO:5002001"). Once user click on the link, user should be able point to new result page.
My current program issue is, the program will point to login page, once user click on email link. When user successfully login, the program will stay on home page instead on new result page.
How can the program point to the new result page after successful login. [My program is use custom authentication scheme for login. And my home page is based on user login setting.]
Anyone can give me some idea how to solve it?
Or anyone have the example to share with me?
Thank you in advance!
Regards,
monica

Hello Monica,
In your "Authentication scheme > Session Not Valid >", if you have specified "login page" or page 101, then try changing this to URL as
f?p=&APP_ID.:101:&SESSION.Regards,
Hari

Is there any way to sent apex reports in mail

Hi All,
I have a requirement to sent an apex report as a mail. Is it possible? Or will I have to write PLSQL procedure to collect the records and embed in html tags and then send the mail
I tried to use <iframe> tag and embed the apex page which is public in to the mail, But it doesn't look good.
Thanks & Regards,
Vikas Krishna

Vikas,
As I understand it, this will be a feature of 4.0. However, for now you must still create them manually. Using public pages, as you've seen, can be tricky. Think about pagination and such.
If an iframe would have "worked" then why not an email with a link back to the right page?
Regards,
Dan
http://danielmcghan.us
http://sourceforge.net/projects/tapigen
http://sourceforge.net/projects/plrecur
You can reward this reply by marking it as either Helpful or Correct ;-)

Web links, email links, button links

I have several different links through out my site. I want them to look differently but it keeps inheriting the styles of my button link. How can I make them appear different. For instance, I don't want my email link to have a background behind it when you hoover. I just want it to change colors. What am I doing wrong. Can anyone help?
HTML
<p>According to the American Society of Civil Engineers (ASCE) the nations bridges are getting a little better – last graded as a “C” (2009) in 2013 they are graded as a “C+”. The ASCE not only has the National Report Card on infrastructure available <a href="http://www.infrastructurereportcard.org/" title="ASCE National Report Card" target="new" class="weblink">(see the 2013 report Card here),</a> they have State and Local reports available as well. <a href="http://www.asce.org/Infrastructure/Report-Card/State-and-Local-Report-Cards/" title="ASCE’s State and Local Report Cards." target="new" class="weblink">ASCE’s State and Local Report Cards.</a></p>
<p>Read the entire Case Study by clicking on the RESOURCES tab and selecting Pavemend Case Studies. Send us a photo and a brief report of your Pavemend repair and get a Pavemend Cap by “Mossy Oak.” <strong><a href="mailto:[email protected]" class="emaillink">[email protected]</a></strong>
</p>
CSS
a.weblink:link, a.weblink:visited, a.weblink:active {
    /* This will handle all the states of the link other than when it is hovered over */
     /* put your style rules in this area */
    color: #0033CC; /* or any other color */
    text-decoration: underline;
a.weblink:hover {
     /* This makes the link Text Hover Color controlable */
     color:#999; /* or whatever color you want that is different from the color that you set for the other statuses */
a.emaillink:link, a.emaillink:visited, a.emaillink:active {
    /* This will handle all the states of the link other than when it is hovered over */
     /* put your style rules in this area */
    color: #0033CC; /* or any other color */
    text-decoration: underline;
    background-color: none;
a.emaillink:hover {
    /* This makes the link Text Hover Color controlable */
    color: #999; /* or whatever color you want that is different from the color that you set for the other statuses */
    background-color: none;
a:link {
    color: #FFFFFF;
    text-decoration: none;
    font-size: 100%;
    padding: 5px;
a:visited {
    color: #FFFFFF;
    text-decoration: underline;
a:hover, a:active, a:focus { /* this group of selectors will give a keyboard navigator the same hover experience as the person using a mouse. */
    text-decoration: none;
    background-color: #03C;
    color: #FFF;
    height: 120%;
    alignment-baseline: text-after-edge;
    /* [disabled]font-size: smaller; */
    text-align: left;
    background-size: 0%;

Not sure what I'm doing wrong. Still not getting it right. Now my footer is wrong also:
CSS
@charset "UTF-8";
/* BEGIN HORIZONTAL DROP-MENU */
.clear-fix:before,
.clear-fix:after {
    content: " ";
    display: table;
.clear-fix:after {
    clear: both;
.clear-fix {
    *zoom: 1;
.sidebarleft img.MgTp {
    margin-top: 185px;
#menu {
    clear: none;
    position: static;
    width: 100%;
    padding-top: px;
    padding-right: px;
    padding-left: px;
    padding-bottom: px;
    background-image: url(_images/topnavpanel.png);
    color: #FFFFFF;
    margin-bottom: 0;
    margin-left: 0;
    margin-right: 0;
    margin-top: px;
    background-repeat: no-repeat;
    float: none;
    text-align: center;
#menu ul {
    margin: 0;
    padding: 0;
    text-align: left;
#menu li {
    list-style: none;
    float: left;
    text-align: center;
    font-family: "Gill Sans", "Gill Sans MT", "Myriad Pro", "DejaVu Sans Condensed", Helvetica, Arial, sans-serif;
    color: #000000;
/**top level menu**/
#menu li a {
    display: inline-block;
    text-decoration: none;
    /* adjust width as needed or use auto */
    width: 13em;
    padding: 8px;
    font-weight: bold;
    line-height: 12px;
    color: #000;
    border-top-style: none;
    font-size: 90%;
    margin-bottom: 0;
    margin-left: 2%;
    margin-right: 2%;
    margin-top: 0;
    border-bottom-style: none;
    text-align: center;
/**top menu style on mouse over**/
#menu li:hover > a {
    color: #FFF;
    width: 13em;
    text-align: center;
/**sub-menu**/
#menu li ul {
    display: none;
    text-align: center;
    padding: 0;
    margin-bottom: 0;
    margin-left: 40px;
    margin-right: 0;
    margin-top: 0;
    border-bottom-style: none;
/**sub-menu, help for older IE**/
#menu li:hover ul, #menu li.hover ul {
    display: block;
    position: absolute;
    z-index: 1000;
    padding: 0;
    text-align: left;
#menu li:hover li, #menu li.hover li {
    float: none;
    background-color: #E1D5BB;
    text-align: left;
/**drop-menu style**/
#menu li:hover li a, nav li.hover li a {
    width: 14em; /* adjust width as needed or use auto */
    margin-top: 0;
/**drop-menu style on mouse over**/
#menu li li a:hover {
    color: #FFF;
    background-color: #03C;
    position: relative;
    text-align: left;
/* Clear floated elements at the end*/
#menu:after {
    visibility: hidden;
    display: block;
    font-size: 0;
    content: " ";
    clear: both;
    height: 0;
/**END HORIZONTAL DROP-MENUS STYLES**/
#pavemendlogo {
    background-image: url(_images/PAVEMEND_LOGO_WHITE.png);
    background-repeat: no-repeat;
    height: 78px;
    width: 196px;
    margin-left: 23px;
    margin-top: -130px;
/**END HORIZONTAL DROP-MENUS STYLES**/
#pavemendlogoresourcepage {
    background-image: url(_images/PAVEMEND_LOGO_WHITE.png);
    background-repeat: no-repeat;
    height: 78px;
    width: 196px;
    margin-left: 23px;
    margin-top: -160px;
/**END HORIZONTAL DROP-MENUS STYLES**/
#slqlogo {
    background-image: url(_images/PMND_SLQ_logo_White.png);
    background-repeat: no-repeat;
    height: 92px;
    width: 225px;
    margin-left: 23px;
    margin-top: -170px;
    margin-bottom: 35px;
#fifteenlogo {
    background-image: url(_images/PMND15Whitesingle.png);
    background-repeat: no-repeat;
    height: 98px;
    width: 225px;
    margin-left: 23px;
    margin-top: -170px;
    margin-bottom: 29px;
    z-index: 1000;
#trlogo {
    background-image: url(_images/PMND_TRlogoWhite.png);
    background-repeat: no-repeat;
    height: 115px;
    width: 225px;
    margin-left: 23px;
    margin-top: -185px;
    margin-bottom: 26px;
    z-index: 1000;
#vrlogo {
    background-image: url(_images/PMND_VRlogoWhite.png);
    background-repeat: no-repeat;
    height: 134px;
    width: 225px;
    margin-left: 23px;
    margin-top: -195px;
    margin-bottom: 18px;
    z-index: 1000;
#dotlinelogo {
    background-image: url(_images/Dotline_White-Red.png);
    background-repeat: no-repeat;
    height: 91px;
    width: 225px;
    margin-left: 23px;
    margin-top: -170px;
    margin-bottom: 35px;
#sllogo {
    background-image: url(_images/SLwhitelogo.png);
    background-repeat: no-repeat;
    height: 92px;
    width: 225px;
    margin-left: 23px;
    margin-top: -170px;
    margin-bottom: 35px;
#ialogo {
    background-image: url(_images/InstantAsphalttopLogo.png);
    background-repeat: no-repeat;
    height: 102px;
    width: 225px;
    margin-left: 23px;
    margin-top: -170px;
    margin-bottom: 25px;
#kemroklogo {
    background-image: url(_images/KEMROK_LOGOWhiteType.png);
    background-repeat: no-repeat;
    height: 52px;
    width: 225px;
    margin-left: 23px;
    margin-top: -150px;
    margin-bottom: 53px;
#kemrokvrlogo {
    background-image: url(_images/KEMROK_LOGO_VR.png);
    background-repeat: no-repeat;
    height: 46px;
    width: 230px;
    margin-left: 23px;
    margin-top: -150px;
    margin-bottom: 59px;
#fireroklogo {
    background-image: url(_images/Firerok_logo_White.png);
    background-repeat: no-repeat;
    height: 81px;
    width: 225px;
    margin-left: 23px;
    margin-top: -155px;
    margin-bottom: 30px;
#awlogo {
    background-image: url(_images/PMNDAWlogowhite1.png);
    background-repeat: no-repeat;
    height: 70px;
    width: 225px;
    margin-left: 23px;
    margin-top: -155px;
    margin-bottom: 40px;
#aslogo {
    background-image: url(_images/PMNDASlogowhite1.png);
    background-repeat: no-repeat;
    height: 64px;
    width: 225px;
    margin-left: 23px;
    margin-top: -155px;
    margin-bottom: 47px;
#prochoicetype {
    background-image: url(_images/pro_choice_concrete_type.png);
    background-repeat: no-repeat;
    height: 27px;
    width: 550px;
    margin-left: 220px;
    margin-top: -40px;
    bottom: px;
    margin-bottom: 66px;
#resourcestype {
    background-image: url(_images/ResourcesType.png);
    background-repeat: no-repeat;
    height: 25px;
    width: 148px;
    margin-left: 220px;
    margin-top: -60px;
    bottom: px;
    margin-bottom: 73px;
#Contacttype {
    background-image: url(_images/PurchaseType.png);
    background-repeat: no-repeat;
    height: 25px;
    width: 151px;
    margin-left: 220px;
    margin-top: -60px;
    bottom: px;
    margin-bottom: 73px;
#Contesttype {
    background-image: url(_images/ContestType.png);
    background-repeat: no-repeat;
    height: 54px;
    width: 478px;
    margin-left: 220px;
    margin-top: -75px;
    bottom: px;
    margin-bottom: 59px;
#sustainabilitytype {
    background-image: url(_images/SustainabilityType.png);
    background-repeat: no-repeat;
    height: 25px;
    width: 179px;
    margin-left: 220px;
    margin-top: -60px;
    bottom: px;
    margin-bottom: 73px;
#techsupporttype {
    background-image: url(_images/TechSupportType.png);
    background-repeat: no-repeat;
    height: 25px;
    width: 761px;
    margin-left: 220px;
    margin-top: -60px;
    bottom: px;
    margin-bottom: 73px;
body {
    background-color: #666;
    color: #000;
    text-align: center;
    background-image: url(_images/roadblurred.png);
    background-repeat: no-repeat;
    background-attachment: fixed;
    background-position: center;
    padding-top: 60px;
    font-family: Verdana, Arial, Helvetica, sans-serif;
    font-size: 100%;
    line-height: 1.4;
.formtext {
    font-size: 100%;
    text-align: left;
.bodyfootnote {
    font-size: 70%;
    margin-left: 20px;
    font-family: Verdana, Arial, Helvetica, sans-serif;
.red {
    font-size: 70%;
    color: #F00;
/* ~~ Element/tag selectors ~~ */
ul, ol, dl { /* Due to variations between browsers, it's best practices to zero padding and margin on lists. For consistency, you can either specify the amounts you want here, or on the list items (LI, DT, DD) they contain. Remember that what you do here will cascade to the .nav list unless you write a more specific selector. */
    padding: 0;
    margin: 0;
    text-transform: capitalize;
    text-decoration: none;
    list-style: none;
    text-align: left;
h1, h2, h3, h4, h5, h6, p {
    /* [disabled]margin-top: 0; */     /* removing the top margin gets around an issue where margins can escape from their containing div. The remaining bottom margin will hold it away from any elements that follow. */
    padding-right: 15px;
    padding-left: 23px;
    line-height: 25px;
h4 {
    padding-left: 0px;
    color: #F40633;
    line-height: 0px;
    font-size: 100%;
h5 {
    padding-left: 23px;
    color: #F40633;
    line-height: 0px;
    font-size: 120%;
a img { /* this selector removes the default blue border displayed in some browsers around an image when it is surrounded by a link */
    border: none;
    margin-left: 0px;
    position: ;
    top: 155px;
    -webkit-box-shadow: 0px 0px 0px 0px;
    box-shadow: 0px 0px 0px 0px;
    left: 9px;
/* ~~ Styling for your site's links must remain in this order - including the group of selectors that create the hover effect. ~~ */
a:link {
    color: #FFFFFF;
    text-decoration: none;
    font-size: 100%;
    padding: 5px;
a:visited {
    color: #FFFFFF;
    text-decoration: underline;
a:hover, a:active, a:focus { /* this group of selectors will give a keyboard navigator the same hover experience as the person using a mouse. */
    text-decoration: none;
    background-color: #03C;
    color: #FFF;
    height: 120%;
    alignment-baseline: text-after-edge;
    /* [disabled]font-size: smaller; */
    text-align: left;
    background-size: 0%;
a.weblink:link, a.weblink:visited, a.weblink:active {
    /* This will handle all the states of the link other than when it is hovered over */
     /* put your style rules in this area */
        background-color: none;
        color: #0033CC; /* or any other color */
    text-decoration: underline;
a.weblink:hover {
     /* This makes the link Text Hover Color controlable */
        background-color: none;
     color:#999; /* or whatever color you want that is different from the color that you set for the other statuses */
a.emaillink:link, a.emaillink:visited, a.emaillink:active {
    /* This will handle all the states of the link other than when it is hovered over */
     /* put your style rules in this area */
    background-color: none;
    color: #0033CC; /* or any other color */
    text-decoration: underline;
a.emaillink:hover {
    /* This makes the link Text Hover Color controlable */
    background-color: none;
    color: #999; /* or whatever color you want that is different from the color that you set for the other statuses */
/* ~~this fixed width container surrounds the other divs~~ */
.container {
    width: 960px;
    background-color: #FFF; /* the auto value on the sides, coupled with the width, centers the layout */
    background-image: url(_images/Bridge4WebScreened.png);
    background-repeat: no-repeat;
    margin-bottom: 0;
    margin-left: 0px;
    margin-right: 0px;
    margin-top: 0;
    text-align: left;
    position: static;
.containerTS {
    width: 960px;
    background-color: #FFF;
    margin: 0 0px; /* the auto value on the sides, coupled with the width, centers the layout */
    background-image: url(_images/US_Map.png);
    background-repeat: no-repeat;
    text-align: left;
/* ~~ the header is not given a width. It will extend the full width of your layout. It contains an image placeholder that should be replaced with your own linked logo ~~ */
.header {
    background-color: #000;
    background-image: url(_images/BannerBlured960.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
    background-size: contain;
.headerSL {
    background-color: #000;
    background-image: url(_images/PMND_SL_Header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerPurchase {
    background-color: #000;
    background-image: url(_images/contact_us_pavemend_header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerSLQ {
    background-color: #000;
    background-image: url(_images/PMND_SLQ_Header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerDOTline {
    background-color: #000;
    background-image: url(_images/DOTLINEHeader.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.header15 {
    background-color: #000;
    background-image: url(_images/PMND15Header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerTR {
    background-color: #000;
    background-image: url(_images/PMND_TRHeader.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerAW {
    background-color: #000;
    background-image: url(_images/anti_wear_pavemend_header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerAS {
    background-color: #000;
    background-image: url(_images/anti_scale_pavemend_header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerVR {
    background-color: #000;
    background-image: url(_images/PMND_VRHeader.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerIA {
    background-color: #000;
    background-image: url(_images/Instant_asphalt_packaged_Header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerKemrok {
    background-color: #000;
    background-image: url(_images/KEMROKpackagedHeader.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerKemrokVR {
    background-color: #000;
    background-image: url(_images/KEMROK_VRpackagedHeader.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerFirerok {
    background-color: #000;
    background-image: url(_images/FIREROKpackagedHeader.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerAntiWear {
    background-color: #000;
    background-image: url(_images/anti_wear_pavemend_header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerTechSupport {
    background-color: #000;
    background-image: url(_images/FEBlurred.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerResources {
    background-color: #000;
    background-image: url(_images/ResourceBanner.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerContact {
    background-color: #000;
    background-image: url(_images/contact_us_pavemend_header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerSustainability {
    background-color: #000;
    background-image: url(_images/Sustainability_topheader.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.header h1 {
    font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
    font-size: 20pt;
    font-style: normal;
    font-weight: bolder;
    color: #FFF;
    padding-top: 150px;
    padding-left: 30px;
/* ~~ These are the columns for the layout. ~~
1) Padding is only placed on the top and/or bottom of the divs. The elements within these divs have padding on their sides. This saves you from any "box model math". Keep in mind, if you add any side padding or border to the div itself, it will be added to the width you define to create the *total* width. You may also choose to remove the padding on the element in the div and place a second div within it with no width and the padding necessary for your design.
2) No margin has been given to the columns since they are all floated. If you must add margin, avoid placing it on the side you're floating toward (for example: a right margin on a div set to float right). Many times, padding can be used instead. For divs where this rule must be broken, you should add a "display:inline" declaration to the div's rule to tame a bug where some versions of Internet Explorer double the margin.
3) Since classes can be used multiple times in a document (and an element can also have multiple classes applied), the columns have been assigned class names instead of IDs. For example, two sidebar divs could be stacked if necessary. These can very easily be changed to IDs if that's your preference, as long as you'll only be using them once per document.
4) If you prefer your nav on the left instead of the right, simply float these columns the opposite direction (all left instead of all right) and they'll render in reverse order. There's no need to move the divs around in the HTML source.
.sidebar1 {
    float: right;
    width: 180px;
    margin-left: 0px;
    margin-right: 30px;
    clear: none;
    font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
    font-size: 100%;
    font-style: italic;
    background-image: url(_images/Testimonialb.gif);
    background-repeat: no-repeat;
    height: 456px;
    text-decoration: none;
    z-index: 1000;
.sidebarPurchase {
    float: right;
    width: 210px;
    margin-left: 0px;
    margin-right: 0px;
    clear: none;
    font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
    font-size: 100%;
    font-style: italic;
    background-image: url(_images/purchaseSB.png);
    background-repeat: no-repeat;
    height: 460px;
    margin-top: 0px;
    text-decoration: none;
    background-color: #217CC0;
    background-position: 10px 10px;
.sidebarPurchasePhoto {
    width: 190px;
    margin-left: 10px;
    margin-right: 20px;
    clear: none;
    font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
    font-size: 100%;
    font-style: italic;
    background-image: url(_images/purchaseSB.png);
    background-repeat: no-repeat;
    height: 127px;
    margin-top: 320px;
    text-decoration: none;
    /* [disabled]background-color: #217CC0; */
    background-position: 10px 10px;
    text-align: center;
.ipadsidebar {
    float: right;
    width: 200px;
    margin-left: 0px;
    margin-right: -20px;
    clear: none;
    font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
    font-size: 100%;
    font-style: italic;
    background-image: url(_images/iPadSidebar.png);
    background-repeat: no-repeat;
    height: 460px;
    margin-top: 0px;
    text-decoration: none;
    background-position: 0px 0px;
    text-align: right;
.sidebarleft {
    float: left;
    width: 200px;
    font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
    font-size: 85%;
    font-style: oblique;
    height: 180px;
    text-decoration: none;
    padding-top: 8px;
    padding-left: 10px;
    margin-right: 5px;
    margin-bottom: px;
    background-color: #217CC0;
    vertical-align: bottom;
    line-height: 120%;
    font-weight: bold;
    border-bottom-style: groove;
    border-bottom-width: 10px;
    margin-top: 0px;
    text-align: left;
.sidebarleftnonav {
    float: left;
    width: 200px;
    font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
    font-size: 85%;
    font-style: oblique;
    height: 180px;
    text-decoration: none;
    padding-top: 8px;
    padding-left: 10px;
    margin-right: 5px;
    margin-bottom: px;
    /* [disabled]background-color: #217CC0; */
    vertical-align: bottom;
    line-height: 120%;
    font-weight: bold;
    border-bottom-style: none;
    border-bottom-width: 10px;
    margin-top: 0px;
    text-align: left;
.sidebarleftresources {
    float: left;
    width: 200px;
    font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
    font-size: 83%;
    font-style: oblique;
    height: 490px;
    text-decoration: none;
    padding-top: 8px;
    padding-left: px;
    margin-right: 5px;
    margin-bottom: px;
    background-color: #217CC0;
    vertical-align: bottom;
    line-height: 120%;
    font-weight: bold;
    border-bottom-style: groove;
    border-bottom-width: 10px;
    margin-top: 0px;
    text-align: left;
.sidebargreen {
    float: left;
    width: 195px;
    height: 410px;
    text-decoration: none;
    padding-top: 20px;
    margin-right: 5px;
    background-color: #8CC63F;
    border-bottom-style: groove;
    border-bottom-width: 10px;
    margin-top: -4px;
    padding-left: 10px;
.nav2 {
    font-family: bebas-neue;
    font-style: normal;
    font-weight: 400;
    color: #FFF;
    text-align: left;
.content {
    width: 730px;
    float: left;
    background-image: none;
    background-repeat: no-repeat;
    background-position: left;
    font-family: "Gill Sans", "Gill Sans MT", "Myriad Pro", "DejaVu Sans Condensed", Helvetica, Arial, sans-serif;
    padding: 10px 0;
    text-align: left;
    font-size: 100%;
    margin-left: px;
.contactform {
    width: 680px;
    background-image: none;
    background-repeat: no-repeat;
    background-position: left;
    font-family: "Gill Sans", "Gill Sans MT", "Myriad Pro", "DejaVu Sans Condensed", Helvetica, Arial, sans-serif;
    padding: 10px 0;
    text-align: left;
    font-size: 90%;
    margin-left: 23px;
    z-index: 1000;
.contestcontactform {
    width: 680px;
    background-image: none;
    background-repeat: no-repeat;
    background-position: left;
    font-family: "Gill Sans", "Gill Sans MT", "Myriad Pro", "DejaVu Sans Condensed", Helvetica, Arial, sans-serif;
    padding-top: 0px;
    padding-right: 0;
    padding-left: 0;
    padding-bottom: 10px;
    text-align: left;
    font-size: 90%;
    margin-left: 23px;
    z-index: 1000;
    margin-top: 100px;
/* ~~ This grouped selector gives the lists in the .content area space ~~ */
.content ul, .content ol {
    padding: 0 15px 15px 40px;
    text-decoration: none;
/* ~~ The navigation list styles (can be removed if you choose to use a premade flyout menu like Spry) ~~ */
ul.nav {
    list-style: none; /* this removes the list marker */
    border-top: 1px solid #666; /* this creates the top border for the links - all others are placed using a bottom border on the LI */
    margin-bottom: 15px; /* this creates the space between the navigation on the content below */
    text-decoration: none;
ul.nav li {
    border-bottom: 1px solid #666;
    text-align: left;
ul.nav a, ul.nav a:visited { /* grouping these selectors makes sure that your links retain their button look even after being visited */
    padding: 5px 5px 5px 15px;
    display: block; /* this gives the link block properties causing it to fill the whole LI containing it. This causes the entire area to react to a mouse click. */
    width: 160px; /*this width makes the entire button clickable for IE6. If you don't need to support IE6, it can be removed. Calculate the proper width by subtracting the padding on this link from the width of your sidebar container. */
    text-decoration: none;
    background-color: #C6D580;
    text-align: left;
ul.nav a:hover, ul.nav a:active, ul.nav a:focus { /* this changes the background and text color for both mouse and keyboard navigators */
    background-color: #DFEBF3;
    color: #FFF;
    text-decoration: none;
    text-align: left;
/* ~~ The footer ~~ */
.footer {
    padding: 10px 0;
    position: relative;/* this gives IE6 hasLayout to properly clear */
    clear: both;
    background-color: #000000;
    height: 150px;
/* ~~ miscellaneous float/clear classes ~~ */
.fltrt { /* this class can be used to float an element right in your page. The floated element must precede the element it should be next to on the page. */
    float: left;
    margin-left: 760px;
.fltlft { /* this class can be used to float an element left in your page. The floated element must precede the element it should be next to on the page. */
    float: left;
    margin-right: 8px;
    margin-left: 23px;
.clearfloat { /* this class can be placed on a <br /> or empty div as the final element following the last floated div (within the #container) if the #footer is removed or taken out of the #container */
    clear:both;
    height:0;
    font-size: 1px;
    line-height: 0px;
.productlogos {
    margin-left: 23px;
    margin-top: 20px;
    float: none;
.Bold {
    font-weight: bold;
.left {
    text-align: left;
.inherent {
    font-style: inherit;
sup {
    position: relative;
    top: -1ex;
    vertical-align:baseline;
    font-size: 75%;
.footer p {
    font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
    font-size: 80%;
    color: #FFF;
    margin-top: 20px;
    margin-bottom: 20px;
    margin-right: 30px;
#wrapper {
     width:970px; /**adjust as needed**/
     margin:0 auto; /**centers page on screen**/
.fltrtpostcard { /* this class can be used to float an element right in your page. The floated element must precede the element it should be next to on the page. */
    float: left;
    margin-left: 720px;
    top: 0px;
    margin-top: -200px;
    margin-bottom: 20px;
    margin-right: 0px;
    height: auto;
.flt_rgt {
    float: right;
    margin-top: 15px;
    margin-right: 30px;
    background-image: ;
    background-repeat: no-repeat;
.flt_pftrgt {
    float: right;
    margin-top: -50px;
    margin-right: 0px;
    background-image: ;
    background-repeat: no-repeat;
.flt_rgtbtmlogo {
    float: right;
    margin-top: 20px;
    margin-right: 30px;
    background-image: ;
    background-repeat: no-repeat;
.flt_rgt2 {
    float: right;
    margin-top: px;
    margin-right: 30px;
    background-image: ;
    background-repeat: no-repeat;
    top: -50px;
    right: -20px;
    padding-top: 0px;
    padding-right: 50px;
.title {
    /* [disabled]margin-right: 30px; */
    margin-top: 0px;
    margin-left: 23px;
    background-image: ;
    background-repeat: no-repeat;
    /* [disabled]margin-left: 20px; */
    top: 30px;
    /* [disabled]margin-top: 30px; */
    left: 30px;
.flt_products {
    float: right;
    margin-right: 30px;
    background-image: ;
    background-repeat: no-repeat;
    margin-left: 500px;
    margin-top: -70px;
.flt_productsb {
    float: left;
    margin-right: 30px;
    background-image: ;
    background-repeat: no-repeat;
    margin-left: 500px;
    margin-top: -80px;
    visibility: inherit;
.flt_productslq {
    float: left;
    margin-right: 30px;
    background-image: ;
    background-repeat: no-repeat;
    margin-left: 350px;
    margin-top: -125px;
.flt_producttr {
    float: left;
    margin-right: 30px;
    background-image: ;
    background-repeat: no-repeat;
    margin-left: 375px;
    margin-top: -125px;
.flt_productvr {
    float: left;
    margin-right: 30px;
    background-image: ;
    background-repeat: no-repeat;
    margin-left: 475px;
    margin-top: -105px;
.flt_productia {
    float: left;
    margin-right: 30px;
    background-image: ;
    background-repeat: no-repeat;
    margin-left: 420px;
    margin-top: -125px;
.flt_productkemrok {
    float: left;
    margin-right: 30px;
    background-image: ;
    background-repeat: no-repeat;
    margin-left: 485px;
    margin-top: -180px;
.flt_productkemrokvr {
    float: left;
    margin-right: 30px;
    background-image: ;
    background-repeat: no-repeat;
    margin-left: 590px;
    margin-top: -170px;
.flt_productfirerok {
    float: left;
    margin-right: 30px;
    background-image: ;
    background-repeat: no-repeat;
    margin-left: 485px;
    margin-top: -170px;
.flt_productaw {
    float: left;
    margin-right: 30px;
    background-image: ;
    background-repeat: no-repeat;
    margin-left: 430px;
    margin-top: -170px;
.flt_product15 {
    float: left;
    margin-right: 30px;
    background-image: ;
    background-repeat: no-repeat;
    margin-left: 280px;
    margin-top: -125px;
.flt_productdotline {
    float: left;
    margin-right: 30px;
    background-image: ;
    background-repeat: no-repeat;
    margin-left: 280px;
    margin-top: -155px;
.flt_productsl {
    float: left;
    margin-right: 30px;
    background-image: ;
    background-repeat: no-repeat;
    margin-left: 370px;
    margin-top: -170px;
.container section nav {
    background-image: url(_images/topnavpanel.png);
    background-repeat: no-repeat;
    height: 30px;
    width: 960px;
    padding-top: 3px;
nav ul {
    list-style: none; /* this creates the space between the navigation on the content below */
    font-size: 90%;
    border-top-width: 0px;
    border-top-style: solid;
    /* [disabled]border-top-color: #666; */
    position: absolute;
    line-height: 120%;
    text-align: left;
nav ul li {
    text-decoration: none;
    color: #FFF;
nav ul a:link , nav ul a:visited { /* grouping these selectors makes sure that your links retain their button look even after being visited */
    padding: 5px 5px 5px 15px;
    display: block; /* this gives the link block properties causing it to fill the whole LI containing it. This causes the entire area to react to a mouse click. */
    width: 160px; /*this width makes the entire button clickable for IE6. If you don't need to support IE6, it can be removed. Calculate the proper width by subtracting the padding on this link from the width of your sidebar container. */
    text-decoration: none;
    text-align: left;
    color: #FFF;
nav ul a:hover, nav ul a:active, nav ul a:focus { /* this changes the background and text color for both mouse and keyboard navigators */
    color: #FFF;
    text-decoration: none;
nav ul a:hover, nav ul a:active, nav ul a:focus { /* this changes the background and text color for both mouse and keyboard navigators */
    color: #FFF;
    text-decoration: none;
    height: 120%;
    width: auto;
    margin-left:;
.orange {
    color: #FAA634;
.white {
    color: #FFFFFF;
.red {
    color: #F00;
.red1 {
    color: #F00;
.toppanel {
    background-image: url(_images/topnavpanel.png);
    background-repeat: no-repeat;
    height: 30px;
    width: 960px;
.white {
.CeraTechLogo {
    background-image: url(_images/CTI_logo_white.png);
    background-repeat: no-repeat;
    width: 200px;
    height: 60px;
#resources {
    background-image: url(_images/ResourcesType.png);
    background-repeat: no-repeat;
    height: 25px;
    width: 521px;
    margin-left: 200px;
    margin-top: -40px;
.pavemendlogo {
    margin-left: 23px;
    margin-top: -130px;
    /* [disabled]margin-top: -40px; */
.footer_img {
    margin-top: -20px;
    margin-left: -10px;
.footer_img2 {
    margin-top: -40px;
    text-align: right;
    float: left;
    margin-right: 35px;
    margin-left: 200px;
footer aside {
    width: 25%;
    float: left;
    text-align: left;
    min-height: 50px;
    margin-left: 23px;
    line-height: 120%;
    font-size: 80%;
    margin-top: 20px;
.aside2 {
    float: none;
    margin-left: 100px;
    width: 29%;
    margin-top: 35px;
.aside3 {
    float: none;
    margin-left: 400px;
    width: 29%;
    line-height: 120%;
    margin-top: -43px;
.sidebarleft img {
    margin-left: -10px;
.sidebarleft icon {
    margin-top: 0px;
    margin-left: -10px;
.sidebarleft nav ul li a img {
    margin-top: 0px;
.content section p a {
    color: #000000;
    font-size: 100%;
/**sub-menu, help for older IE**/
.content section p a:hover ul {
    display: block;
    position: ;
    z-index:1000;
    padding: 0;
.content section p a:hover li, .content section p a li.hover li {
    float: none;
    background-color: #E1D5BB;
/**drop-menu style**/
.content section p a:hover li a, nav li.hover li a {
    width: 14em; /* adjust width as needed or use auto */
    margin-top: 0;
/**drop-menu style on mouse over**/
.content section p a:hover {
    position: relative;
    background-color: none;
    background-image: ;
    background-image: ;
    height: 120%;
    width: 120%;
    overflow-y: hidden;
    overflow-x: hidden;
    visibility: visible;
    font-weight: bold;
    color: rgba(255,255,255,1.00);
/* Clear floated elements at the end*/
.content section p a:after {
    visibility: hidden;
    display: block;
    font-size: 0;
    content: " ";
    clear: both;
    height: 0;
#firstname {
    width: 330px;
    margin-top: 0px;
#lastname {
     width:330px;
#streetaddress {
     width:684px;
#city {
     width:330px;
#zip {
     width:260px;
#company {
     width:684px;
#phone {
     width:330px;
#email {
     width:330px;
#outsidetheus {
     width:330px;
HTML
<!doctype html>
<html>
<head>
<meta charset="UTF-8">

<title>Permanent Concrete and Asphalt Repair Home Page</title>
<meta name="description" content="CeraTech's Pavemend family of high performance concrete repair products have become the choice of professionals across the country for their rapid return to service, versatility, ease of use, and superior durability.">

<link href="../pavmend_styles.css" rel="stylesheet" type="text/css">
<style type="text/css">
a:link {color:blue}
a:visited {color:black}
a:hover,
a:active,
a:focus {background:blue; color:white}
.weblink a:link {color:blue}
.weblink a:visited {color:yellow}
.weblink a:hover,
.weblink a:active,
.weblink a:focus {background:none; color:red}
.email a:link {color:green}
.email a:visited {color:silver}
.email a:hover,
.email a:active,
.email a:focus {background:none; color:navy}
</style>


</head>
<body>
<div id="wrapper">
<div class="container">

<div class="header"></div>
<div id="pavemendlogo"></div>
      <div id="prochoicetype"></div>

<nav>
    <ul id="menu">
      <li><a href="../pavemend_home_page.html">OUR PRODUCTS ▼</a>
        <ul>
          <li><a href="../slq_product_page.html">SLQ<sup>®</sup> - Very Rapid Repair Mortar</a></li>
          <li><a href="../sl_product_page.html">SL<sup>®</sup> - Semi-Leveling Rapid Repair Concrete</a></li>
          <li><a href="../dotline_product_page.html">DOTLine™ - Pre-Extended Rapid Repair Concrete</a></li>
          <li><a href="../15.0_product_page.html">Pavemend 15.0<sup>®</sup> - Self Leveling Rapid Repair Mortar</a></li>
          <li><a href="../TR_product_page.html">Pavemend TR<sup>®</sup> - Semi-Leveling Rapid Repair Mortar</a></li>
          <li><a href="../VR_product_page.html">Pavemend VR<sup>®</sup> - Vertical & Overhead Rapid Repair Mortar</a></li>
          <li><a href="../IA_product_page.html">Instant Asphalt™ - Permanent Asphalt Repair Material</a></li>
          <li><a href="../kemrok_product_page.html">KEMROK™ - Chemical Resistant Repair Concrete</a></li>
          <li><a href="../kemrokVR_product_page.html">KEMROK VR™ - Vertical & Overhead Chemical Resistant Repair Mortar</a></li>
          <li><a href="../firerok_product_page.html">FIREROK™ - High Temperature Repair Concrete</a></li>
          <li><a href="../antiwear_product_page.html">Anti-Wear™ - Reactive, Concrete Surface Hardener</a></li>
          <li><a href="../antiscale_product_page.html">Anti-Scale™ - Reactive, Concrete Surface Hardener</a></li>
        </ul>
      </li>
      <li><a href="../resources_page.html">RESOURCES</a></li>
      <li><a href="../technical_support.html">TECHNICAL SUPPORT</a></li>
      <li><a href="../contact_page.html">CONTACT US</a></li>
    </ul>
</nav>

</section>

<div class="sidebar1">
    
</div>


<div class="content">
    <p>
    <section>
        <p> </p>
<img src="../_images/homeheader.png" alt="" width="650" height="31" class="fltlft"/>
    </section>
    </p>
    <p> </p>
</section>
    <p> </p>
      <section><p><strong>Pavemend</strong><sup>®</sup> concrete and asphalt repair products are quickly becoming the preferred repair materials for Turnpike, State DOT bridge crews and discriminating engineers who recognize the value of durable, permanent concrete and asphalt repairs. Contractors and maintenance personnel save time, reduce repair costs, and minimize exposure to traffic and traffic disruptions.</p>
        <h3>Concrete & Asphalt repair applications include:</h3>
        <table width="700" align="left" >
          <tr>
            <td valign="top" nowrap style="padding-left: 15px;">Full & Partial Depth Bridge Deck Repairs </td>
            <td valign="top" nowrap style="padding-left: 15px;">Dowel Bar Retrofits</td>
            <td valign="top" nowrap style="padding-left: 15px;">Industrial Concrete Repair</td>
          </tr>
          <tr>
            <td valign="top" nowrap style="padding-left: 15px;">Bridge Header Joints</td>
            <td valign="top" nowrap style="padding-left: 15px;">Cold Weather Repairs</td>
            <td valign="top" nowrap style="padding-left: 15px;">Concrete Exposed to High Heat </td>
          </tr>
          <tr>
            <td valign="top" nowrap style="padding-left: 15px;">Bridge Approach Slabs</td>
            <td valign="top" nowrap style="padding-left: 15px;">Runway Repairs</td>
            <td valign="top" nowrap style="padding-left: 15px;">Concrete Exposed to Chemicals</td>
          </tr>
          <tr>
            <td valign="top" nowrap style="padding-left: 15px;">Form & Pour Repairs</td>
            <td valign="top" nowrap style="padding-left: 15px;">Utility Trenches</td>
            <td valign="top" nowrap style="padding-left: 15px;">Concrete Exposed to Wastewater</td>
          </tr>
          <tr>
            <td valign="top" nowrap style="padding-left: 15px;">Joint Nosings</td>
            <td valign="top" nowrap style="padding-left: 15px;">Post Grooving Treatments</td>
            <td valign="top" nowrap style="padding-left: 15px; padding-bottom: 30px;">Manhole Rehabilitation</td>
          </tr>
        </table>
<h3>Sustainable Concrete and Asphalt Repair Technology</h3>
<p>Featuring technology developed in the USA, Pavemend products require only the addition of water, no bonding agents or curing compounds. Pavemend concrete and asphalt products are easier to use, offer greater durability provide, superior return on investment, and are by the far the most sustainable repair products available today.</p>
      </section>
            <p> </p>
</div>


<footer>
         <img src="../_images/productfamily.png" alt="" width="250" height="80" class="flt_products"/>
<div class="footer"><img src="../_images/Done_Smart_White_Logo.png" alt="done_smart_white" width="150" height="17" class="flt_rgt" />
<aside><strong><em style="color: #FFF; font-size: 90%;">Manufactured by</em></strong><br><br>
<img src="../_images/CTI_logo_white.png" alt="" width="200" height="47" class="footer_img"/></aside>
<aside class="aside2"><a href="#../twitter.com/Pavemend"><strong><em>Twitter</em></strong> <img src="../_images/twitter-bird-dark-bgs.png" width="20" height="17" alt=""/></a></aside>
<aside class="aside3"><strong><em style="color: #FFF"><a href="../sustainability_page.html">Planet Friendly Technology</a></em></strong><br>
<a href="../sustainability_page.html"><img src="../_images/PFTLogo.png" alt="Planet Friendly Technology" width="75" height="73" class="footer_img2" title="Planet Friendly Technology"/></a></aside>
</footer>
    </div>
</div>

</body>
</html>
I feel like I'm making a mess of it.

SQL report link to another report

Hello,
I am using Apex 4 and trying to link an sql report with another report. If I were able to use an interactive report I could easily link that to another page, but that would require me to have a primary key. The problem is that I need to link a few tables. So two questions:
1.) Can I link these via an HTML link to my other page? I would have a HTML link in my report that would link via URL parameter passing. So can I use HTML in a report?
2.) What is the syntax for a parameter passing via URL? Here is my link that would be:
a href= f?p=107:40:&APP_SESSION::::P40_NAME:MARK: Are there any other ways to accomplish this?
Thanks,
Mark
Edited by: LondonMark on 23-May-2011 04:18
Edited by: LondonMark on 23-May-2011 04:20

I am using Apex 4 and trying to link an sql report with another report. If I were able to use an interactive report I could easily link that to another page
It's easy in standard reports< /a>. (Ignore the "Interactive Report" typo in step 1.)
1.) Can I link these via an HTML link to my other page? I would have a HTML link in my report that would link via URL parameter passing. So can I use HTML in a report?You can, but it's better practice to keep data retrieval and HTML structure separate when possible—in this case by using declarative Column Links.
2.) What is the syntax for a parameter passing via URL?This is also covered in the documentation.
Here is my link that would be: a href= f?p=107:40:&APP_SESSION::::P40_NAME:MARK:
{quote}
That looks to have the order of the parameters correct, but it's missing some syntax:<a href="f?p=107:40:&APP_SESSION.::::P40_NAME:MARK">...</a>
The static text exact substitution method of referencing the value of an APEX item requires a terminating dot ("."): <tt>&APP_SESSION.</tt>

Clickable email link in apex report

Similar Messages

Maybe you are looking for