RMS form Button image issue

On RMS forms Button image is not coming. I think this is some confguration issue but i am not able to locate the configuration file which is responsible for this issue.

I think this is a better way to implement your UI:
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml">
  <mx:Spacer height="2%"/>
  <mx:Panel width="55%" height="28%" title="User Details" paddingTop="10">
    <mx:Form>
      <mx:FormItem label="Select account type: " letterSpacing="1"
        fontFamily="Arial" >
          <mx:ComboBox id="accCombo" />
      </mx:FormItem>
      <mx:FormItem label="UserName: " letterSpacing="2" fontSize="11"
        fontFamily="Arial">
        <mx:TextInput id="uname" width="100%"/>
      </mx:FormItem>
      <mx:FormItem label="Password: " letterSpacing="2"
        paddingTop="30" fontSize="11" fontFamily="Arial">
        <mx:TextInput id="password" width="100%" displayAsPassword="true"/>
      </mx:FormItem>
      <mx:FormItem label="Retype Password: " letterSpacing="2"
        paddingTop="30" fontSize="11" fontFamily="Arial">
        <mx:TextInput id="password1" width="100%"
          displayAsPassword="true"/>
      </mx:FormItem>
    </mx:Form>
  </mx:Panel>
</mx:Application>
If this post answers your question or helps, please mark it as such.

Similar Messages

  • Button image issues

    Im having issues with button images in captivate 4, after designing buttons in photoshop then saving them as PNG's and putting them in the buttons folder. When i apply these buttons to a slide the button images are missing parts and look bad.. any suggestions?, please help.

    Hi there
    I believe Captivate uses the color value of the pixel in position 0, 0 to determine the transparent color for the button image. You need to ensure you are using a unique color for that location. What you posted seems to infer that you have a color being rendered as transparent and the color is used in other places in the image.
    Cheers... Rick
    Click here for Adobe Certified Captivate and RoboHelp HTML Training
    Click here for the SorcerStone Blog
    Click here for RoboHelp and Captivate eBooks

  • Form button does not work when a program is moved from Windows 8.2 to Windows 7

    Hi,
    I have a few Excel programs which use the ODBC to get data from Access and which have macros which writes data to an external program, MYOB.
    When the macros tries to write the data to MYOB it fails if I am not running the program in administrator mode.   It seems that Windows 8.2 has a different level of security than Windows 7 and must be run in administrator mode for the ODBC to work. 
    I have had issues after running the program in administrator mode (testing) if I simply do a save (in administrator mode) and then send it to the customer.   The issue is that it just will not work on the customer's site.   I have gotten
    around this in the past by saving any changes, going back out of excel, loading the program again (not in administrator mode) and saving it - before sending it to the customer.   This worked until now.
    For some unknown reason, the last time I sent a program to the customer and carried out the above process, the program stopped working.   Originally I thought that the macro just wouldn't work on windows 7, but eventually found that it is the form button
    that will no longer work when the program is moved from 8.2 to 7.
    Does anyone know why there is an incompatibility between 8.2 and Windows 7 and what I should be doing to ensure that my programs work in my customers environment(windows7)?
    In the meanwhile, I have changed the form button to an activex button and the program works fine in both environments.
    Thanking you in advance,

    there is some OP report after Windows update Dec 2014 macro stop responding ( I cant confirm if this is also related to your issue) its because security update for Office maybe conflict with the active-x that you are installed
    try to
    Close Excel
    Start Windows Explorer.
    Select your system drive (usually C:)
    Use the Search box to search for *.exd
    Delete all the files it finds.
    Start Excel again
    Open that file and save it, and try open at Windows 7
    to get more detail about this issue, I suggest also contact Office forum
    this case also will be solve installing kb3025036
    good luck

  • Standard button image problem

    Hi,
    I've got a problem when I try to set Image to the button from standard components.. I can set it up, but than I didn't see the image in the browser.
    With the button from basic components there is everything working fine, unfortunately I need that component from standard.. any advice?
    thx.

    Hi,
    I've got a problem when I try to set Image to the button from standard
    components.. I can set it up, but than I didn't see the image in the browser.
    With the button from basic components there is everything working fine,
    unfortunately I need that component from standard.. any advice?
    thx.Standard button has problems with images due to a JSF issue. To work around the issue, remove leading / from the buttons image property and re-deploy. This should cause the standard button image to display correctly.
    Hope it helps,
    Lark

  • Reset Form button showing as Submit Form button?

    Hello....
    I have run into an odd issue that I can not figure out.  For the past year, I have been creating and manually distributing various forms to our Sales Engineering group and outside partners.  These forms are all designed from a common template we developed that includes a standard “Reset Form” button.  Upon sending out a new form, I received an email with a screen shot that showed the Reset Form button as “Submit Form”.  The partner went on to say that they thought it was the same as another form they have from me, which also shows a Reset Button as “Submit Form”
    The end user states they are using Adobe 8.1.4.  The forms were developed (9 Pro) LC Designer ES 8.2 and are set to be 8.0 or higher compatible.  This is the first time I have heard of this and cannot figure out the cause.  The label on the canned button itself is being changed from Reset to Submit. 
    Does anyone have any thoughts as to what would cause this and how to correct?  I can not assume that this is the only time this has happened, but it is the first I am hearing of it.
    Thank you and my apologies if this should have gone to another forum group 
    Chris Link, CTS, EAVA
    Sr. Design Engineer

    I have not heard of this before .....can you send the template to [email protected] so I can investigate? Please include a description of the issue in the email.
    Paul

  • Button Image not display proper in production.

    Hi,
    I have issue regarding button image, in local jdev its works fine but when i deploy page to production button image is not shown properly. Its display like html button. can any body tell me the solution?
    Thanks

    Also go through
    Look and Feel for "Button"Thanks
    --Anil                                                                                                                                                                                                                       

  • Using css on form buttons to make them pretty

    Hello,
    I usually use the below css (bottom page) on a page for my
    form buttons, it
    works nicely in ff and IE, but with regards to the W3C CSS
    Validator I get
    the following errors.
    input.btn attempt to find a semi-colon before the property
    name. add it
    input.btn Property progid doesn't exist : DXImageTransform
    input.btn Parse Error DXImageTransform.Microsoft.Gradient
    (GradientType=0,
    StartColorStr='#ffffffff', EndColorStr='#ffeeddaa');
    input.btn Parse Error }
    If any one knows how to make this errorless I would be
    grateful, it does
    appear as a nice botton etc lol
    any way if any one has input I am grateful
    regards
    k
    -~-~-~-~-~-~ the page with botton is below -~-~-~-~-~-~
    <%@LANGUAGE="VBSCRIPT" CODEPAGE="65001"%>
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01
    Transitional//EN"
    http://www.w3.org/TR/html4/loose.dtd">
    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html;
    charset=utf-8">
    <title>Testing css form button</title>
    <style type="text/css">
    <!--
    input.btn {
    color:#050;
    font-family: Tahoma, Arial, Verdana, Monaco, sans-serif;
    font-size:10px;
    font-weight:bold;
    background-color:#fed;
    cursor:pointer;
    border:1px solid;
    border-top-color:#B2876A;
    border-left-color:#B2876A;
    border-right-color:#B2876A;
    border-bottom-color:#B2876A;
    filter:progid:DXImageTransform.Microsoft.Gradient
    (GradientType=0,
    StartColorStr='#ffffffff', EndColorStr='#ffeeddaa');
    -->
    </style>
    </head>
    <body><form action="" method="post">
    <p>
    <input name="ahithere" type="submit" class="btn"
    id="ahithere"
    value="Submit">
    </form>
    </body>
    </html>

    .oO(Thierry)
    >"Michael Fesser" <[email protected]> wrote in message
    >news:[email protected]...
    >> .oO(Thierry)
    >>
    >>>Following Micha's advice will make your document
    validate, but... this
    >>>will
    >>>also add a HTTP request.
    >>
    >> Correct, but only in IE 6. And who really cares
    about that?
    >>
    >> Additionally many modern and sophisticaded layouts
    usually need some
    >> more workarounds for IE 6 than just a filter here
    and an alpha loader
    >> there. It makes sense to use a separate stylesheet
    for them, because
    >> IE-specific hacks in the main stylesheet may cause
    even more problems
    >> and also affect other browsers.
    >
    >I used to think that way [1], but I changed my mind...
    >imho:
    >- keeping rules together facilitate maintenance.
    Sure, but some rules are only required for IE. They don't
    make sense for
    all other browsers and would just clutter up the real CSS,
    particularly
    if you have to use hacks to apply them to IE only.
    >- using CCs for IE may create extra HTTP requests for
    that browser only, but
    >it adds extra markup for *all* browsers.
    Indeed. But how much does it take on each page usually? 50
    bytes? 100?
    A real example from my own sites with CCs for both IE 6 (CSS
    and JS) and
    IE 7 (only CSS) is exactly 363 bytes - peanuts.
    I also use a lot of 'link' elements for example (next page,
    previous,
    home, search, etc.) All users have to download them, even
    though most
    won't recognize them, because only very few browsers support
    these meta
    navigation links natively. But for those whose browsers
    interpret them,
    they're a useful addition. And the rest has to download 1KB
    more -
    doesn't matter.
    >- you say who cares about IE6
    Hmm, it was not properly worded ... what I meant was more
    like this: I
    _do_ care about IE 6 (I have to, like most of us), but I
    don't really
    care if it has to download one or even ten additional files.
    In fact on my sites there are some more files for IE 6 only:
    a CSS, a
    JS, a behaviour file for fixing its PNG issue and maybe some
    JPEGs as
    replacements where the PNG fix doesn't work. So there are at
    least 4
    additional files for IE 6 only, but since they're necessary I
    don't
    worry about these additional HTTP requests.
    >but when IE6 is gone for good, you end up
    >with unecessary comments in all your documents rather
    than useless CSS
    >filters in a (few) styles sheets
    When IE 6 is dead, it's no problem to remove this single line
    from my
    page templates. One little change on each site - won't take
    long.
    And as said, usually there's a bit more than just filters. An
    example:
    http://static.andreas-pauli.de/css/ie6.css
    There's not even a PNG fix in this case. All these rules are
    related to
    IE's float problems, to give some elements "layout" or to
    overcome other
    little ugly glitches. Having all these in the main CSS would
    make things
    much more complicated and almost impossible to remove when IE
    6 becomes
    obsolete one day.
    >- afaik, wellknown IE specific hacks as such as the
    *property or _property
    >hack are totally safe to use (as long as they are always
    followed by a ";")
    This is my main problem. No hack is totally safe. If I have
    the choice
    between a rather ugly, but documented behaviour and a hack, I
    definitely
    prefer the first one. Even though the common IE hacks are
    well-tested
    these days and I don't expect real side effects, there's
    always a kind
    of a negative connotation. I simply don't like them.
    Additionally there's the problem that in my case IE 7
    requires some
    fixes as well, and then things would become really
    complicated if you
    only want to use hacks. CCs are ugly and pollute the markup a
    bit, but
    at least they are a reliable way to give each IE the medicine
    it needs.
    Personally I consider them the only useful & working
    feature in IE. ;-)
    >fwiw, I'm a strong advocate for markup validation
    Me too.
    >but I don't care when CSS
    >files fail validation (actually I don't expect them to
    validate).
    Well, I prefer valid CSS too, but don't care too much about
    warnings.
    For example I usually get tons of warnings when I declare a
    foreground
    color without a background or the other way round. But this
    is by
    intention, and since I know what I'm doing (at least in most
    cases), I
    think I can safely ignore these warnings. But I don't like
    errors. And
    as said - my main problem are the hacks, which I try to
    avoid.
    So there's not only technical issues in these cases, but also
    a lot of
    personal preferences I think. For me CCs are the cleaner way
    and much
    easier to handle. YMMV, of course.
    Micha

  • Calling Webservice from Adobe form - Webservice URL  Issue

    Dear Friends,
      I have developed a webservice and calling it from an Adobe form. I have downloaded the WSDL file from tcode SOAMANAGER. When I create a data connection from the Adobe form  I use this WSDL file and the form elements gets created automatically and I drag and drop them into the form. The issue is when I click on the Submit(Execute) button the Webservice URL is always pointed to the client from where the file was downloaded and its hard-coded ( for example if i download the wsdl file from client 300 then the URL would be http://<location>/sap/bc/srt/rfc/sap/z_web_getmat/300/z_web_getmat/z_web_getmat). So if i execute the form from client 200 its not working. How to make this URL dynamic so that the webservice gets executed from the client from where this form is called. Please advice.
    Regards
    Sapient

    Hi,
    You have to handle it in your form on submit button calling the web service:
    Write below java script code at submit event to change the URL at run time:
    var tempsoapAddress = xfa.connectionSet.DataConnection.getElement("soapAddress").value;
    var tempwsdladdress = xfa.connectionSet.DataConnection.getElement("wsdlAddress").value;
    var ServerPath = body.systemConfig.system.rawValue;
    var client = <Get Client from a data attribute>
    var Soap_PreServerPort =  "http://";
    var Soap_PostServerPort =  "/sap/bc/soap/rfc?sap-client=";
    var SoapAddress = Soap_PreServerPort + ServerPath + Soap_PostServerPort + client ;
    var Wsdl_PreServerPort =  "http://";
    var Wsdl_PostServerPort1 =  "/sap/bc/soap/wsdl11?services=ZBAPI_PO_CREATE2&amp;sap-client=";
    var wsdlAddress =  Wsdl_PreServerPort + ServerPath + Wsdl_PostServerPort1 + client ;
    xfa.connectionSet.DataConnection.getElement("soapAddress").value = SoapAddress;
    xfa.connectionSet.DataConnection.getElement("wsdlAddress").value = wsdlAddress;
    xfa.connectionSet.DataConnection.execute(0);
    xfa.connectionSet.DataConnection.getElement("soapAddress").value = tempsoapAddress;
    xfa.connectionSet.DataConnection.getElement("wsdlAddress").value = tempwsdladdress;
    xfa.connectionSet.DataConnection = null;
    Change the variable wsdlAddress as per your requirement. The above code is just a sample.
    For getting the client pass it in a datasource variable attribute at time of downloading the form. At time of submit get the value of that variable and use it to form the url.
    Regards,
    Vaibhav

  • How do I remove the Submit Form button?

    I am using Acrobat Pro 9 with LiveCycle. I have created an interactive form and did not include a button to e-mail the form. When the distributed form is opened, there is a purple bar across the top with instructions to click "Submit Form" and  "Highlight Fields" and "Submit Form" buttons. I do not want this form e-mailed back to me. It just needs to be saved by the user and uploaded at a later time. Saving it after the user fills in the fields is not the issue. That is working fine. But the user may be confused by a button saying they should submit the form. Plus it is my e-mail address in the field and I don't want all these forms showing up in my e-mail box. This happens whether I choose to distribute it with "Automatically download..." or "Manually collect..."
    Does anyone know what can be done to prevent the form from displaying the "Submit Form" button?
    Also, one user did get get a warning when saving about that not being the optimal way to send the data. I believe it said to press submit form. I'm sorry, I was not relayed the exact warning, but it was something to that effect. It did, however, save correctly.

    Pzaidel: YOU are a freakin genius. Great suggestion-worked perfectly! Here's how I did it with a form created in Indesign:
    Do entire backgrnd layout in Indesign-convert to regular PDF.
    Open New doc in LC-standard way-create all fields.
    After completion when you open it in Adobe Acrobat, you will see the "Submit Form" at the top next to "Highlight existing fields".
    Go back to your LiveCycle doc and:
    Highlight and ctrl+c copy all fields onto clipboard. [I don't think there is an option to copy fields anywhere within LC]
    Do as Pzaidel suggests above: create new LC form [you cannot avoid selecting interactive form....but didn't seem to matter].
    Import your PDF layout from InDesign [or word].
    THEN Paste all fields back into form.
    TA DA! No submit button.
    AND after importing and placing all fields, I even included a print button that works on the bottom of the form so anyone could see-it must be printed and cannot be submitted-at least by a button.
    Thanks so much for the fix!!

  • I'VE CREATED A FORM WITH IMAGES. WHEN I OPEN THE FILE IN ACROBAT READER, THE IMAGES ARE BALCK BOXES!

    I'VE CREATED A FORM WITH IMAGES. WHEN I OPEN THE FILE IN ACROBAT READER THE IMAGES ARE BLACK BOXES.
    THE FORM HAs (extend features to acrobat reader). THE FORM WAS DISTRIBUTED.
    NON OF MY EMPOYEES CAN SEE THE IMAGES. WHAT'S WRONG? CAN YOU HELP?

    However, the view large images is an issue for a form that is being distributed. Either a note needs to be added to the PDF to tell how to enable the view or the images need to be changed so that the enabling is not needed.

  • Question:   how to resize form buttons in a CSS

    I have a question.   I am trying to implement some PayPal features into my website with some their custom button functionality.   In normal HTML, the buttons look fine.  But using a CSS template, the form buttons get squashed and funny looking.   Is there an easy way to resize them?
    (I'm using Dreamweaver CS4 on a WinVista machine)  
    Any help is greatly appreciated. 
    -ryan

    and here is the ENTIRE CSS file
    CSS Credit: http://www.templatemo.com/
    body {
        margin:0;
        padding:0;
        line-height: 1.5em;
        font-family:  Helvetica, Arial, sans-serif;
        font-size: 11px;
        color: #FFFFFF;
        background: #FFFFFF;
    h1 {
        margin: 0 0 25px 0;
        padding: 10px 0 10px 15px;
        font-size: 20px;
        font-weight: bold;
        color: #ffc601;
        background: #000000;
        border-bottom: 1px solid #b4a08a;
    h2 {
        width: 235px;
        height: 25px;
        padding: 15px 0 0 35px;
        margin: 0 0 25px -10px;
        font-size: 16px;
        color: #6c5b4c;
        background: url(images/left_heading_background.gif) no-repeat;
    h3 {
        margin: 0 0 5px 0;
        padding: 0;
        font-weight: bold;
        font-size: 14px;
        color: #ffc601;   
    h4 {
        margin: 0 0 5px 0;
        padding: 0;
        font-weight: bold;
        font-size: 12px;
        color: #999999;
        text-align: center;
    .rantsection {
        height: 13px;
        margin-bottom: 10px;
    .rantsection img {
        float: left;
        height: 13px;
        width: 13px;
        border: 0px;
        margin-right: 5px;
    a:link, a:visited { color: #999999; text-decoration: none;}
    a:active, a:hover { color: #999999; text-decoration: underline;}
    .more_button a{
        clear: both;
        text-align: center;
        display: block;
        width: 60px;
        padding: 1px 0;
        margin-bottom: 5px;
        background: #6c5b4c;
        border-bottom: 1px solid #a59180;
        color: #FFFFFF;
        font-weight: bold;
        text-decoration: none;
    .download_button a{
        float: right;
        text-align: center;
        width: 65px;
        padding: 1px 0;
        background: #6c5b4c;
        border-bottom: 1px solid #a59180;
        color: #FFFFFF;
        font-weight: bold;
        text-decoration: none;
    img {
        border: 1px solid #6c5b4c;
    /* ----- Form ----- */
    .form_row{
        margin-bottom: 3px;
    form{
        margin: 0;
        padding: 0;
        text-align: right;   
    label {
        margin-right: 10px;
    input{
        width: 130px;
        height: 18px;
        padding: 1px 0;
        line-height: normal;
        color: #99836c;
        border: 1px solid #99836c;
        background: #400a0a;
        font-size: 14px;
    select{
        color: #99836c;
    .button{
        width: 60px;
        line-height: normal;
        margin: 0;
        height: 23px;
    /* End of Form */
    #container {
        margin: 0px auto;
        width: 970px;
        background: url(images/main_background.gif) repeat-y;
    /*------------ Header --------------- */
    #header {
        float: left;
        width: 900px;
        padding: 0 35px;
        margin: 15px 0 10px 0;
    #title {
        float: left;
        width: 300px;
    #sitetitle {
        padding: 30px 0 10px 0;
        font-size: 4.0em;
        font-weight: bold;
        color: #FF9933;
    #sitetitle span{
        font-weight: normal;
        color: #FFFFFF;
    #login {
        float: right;
        margin-top: 25px;
        width: 300px;
    /* -------------- End of Header------------------ */
    /* --------- Banner ---------- */
    #banner {
        clear: both;
        width: 970px;
        height: 256px;
        background: url(images/banner.jpg) no-repeat;
    #banner_text {
        padding: 60px 0 0 225px;
        width: 550px;
    #banner_title{
        margin: 0 0 25px 0;
        padding: 0;
        font-size: 24px;
        font-weight: bold;
        color: #ffc601;
    #banner_text p{
        margin: 0 0 25px 0;
        padding: 0;
    /* --------- End of Banner ---------- */
    /*--- Menu ---*/
    #menu{
        float: left;
        width: 970px;
        height: 51px;
        background: url(images/menu_background.gif) no-repeat;
    #menu ul {
        float: left;
        margin: 0;
        padding: 10px 0 0 40px;
        list-style: none;
    #menu ul li{
        display: inline;
    #menu ul li a{
        float: left;
        width: 140px;
        height: 20px;
        margin-top: 10px;
        padding: 0;
        font-size: 1.1em;
        font-weight: bold;
        text-align: center;
        text-decoration: none;
        color: #CCCCCC;
        border-right: 1px solid #CCCCCC;
    #menu ul li .lastmenu{
        border-right: none;
    #menu li a:hover, #menu li .current{
        color: #FFCC33;
    /*--- End of Menu ---*/
    /*--- Content ---*/
    #content {
        float: left;
        margin: 0;
        padding: 0 10px;
        width: 950px;
        color: #FC3;
        text-align: center;
    /*--- Left Column---*/
    #left_column {
        float: left;
        margin: 20px 10px 0 0;
        padding: 0px;
        width: 235px;
    .left_col_box {
        margin: 0 0 25px 25px;
        color: #AAA;   
    .blog_box {
        padding-bottom: 15px;
        margin-bottom: 15px;
        border-bottom: 1px solid #220404;
    .blog_box h3 a{
        font-size: 12px;
        color: #d3a401;   
    .blog_box span{
        color: #99836c;
    /*--- End of Left Column---*/
    /*--- Right Column---*/
    #right_column {
        float: right;
        margin: 25px 25px 0 0;
        padding: 0;
        width: 650px;
    .right_panel_fullwidth {
        float: left;
        width: 650px;
        padding: 0 0 25px 0;
    .right_panel_fullwidth img{
        float: left;
        margin: 3px 10px 0 0;
    .right_panel_fullwidth_content {
        float: left;
        width: 620px;
        padding: 0 15px 25px 15px;
    .right_panel_fullwidth_content p{
        text-align: justify;
    #new_released_section {
        float: left;
        width: 650px;
        margin: 0 0 30px 0;
    .new_released_box {
        float: left;
        width: 180px;
        margin: 0 10px 0 15px;
        text-align: center;
    .new_released_box img{
        margin-bottom: 5px;
    #news_section {
        float: left;
        width: 310px;
        margin: 0 25px 0 0;
    .news_box {
        float: left;
        width: 280px;
        margin: 0 15px 25px 15px;
    .news_box img{
        float: left;
        width: 110px;
        margin: 3px 10px 0 0;
        border: 1px solid #333333;
    .news_box p{
        margin: 0;
        padding: 0;
    #topdownload_section {
        float: right;
        width: 300px;
        padding: 0;
        margin: 0;
        background: #99836c;
    .topdownload_box {
        float: left;
        width: 270px;
        padding-bottom: 5px;
        margin: 0 15px 10px 15px;
        color: #24211d;
        font-weight: bold;
        border-bottom: 1px solid #6b5946;
    * html .topdownload_box {
        margin: 0 15px 10px 7px;
    .topdownload_box span{
        font-weight: normal;
    .title_singer{
        float: left;
        width: 200px;
    /*--- End of Right Column---*/
    /*--- End of Content ---*/
    /* ----- Footer ----- */
    #footer {
        clear: both;
        padding: 15px 0;
        width: 950px;
        margin: 0 10px;
        text-align: center;
        color: #000000;
        background: #6c5b4c;
        text-align: center;
    #footer a{
        color: #000000;
    #footer a:hover{
        color: #cccc66;
    /* ----- End of Footer ----- */
    #container #content #right_column #new_released_section .new_released_box h3 {
        text-align: center;

  • How to remove "submit form" button that's generated when distributing form without Designer

    When I open it in Designer to delete the image all of my java gets screwed up, so I'm hoping there is a solution that doesn't involve updating all of the code. I'm using PDF Expert 5 and Box because adobe's reader is absolute garbage.
    Thank you in advance!

    Sorry for not being clear, LC Designer.
    Here is a screenshot of the submit form button in a blank form that's automatically inserted when distributing. If I open it in LC Designer I can remove the submit form button but it screws up all java and formatting. (sorry for not inserting an image or link, adobe'ss forums are about as well developed as its software)
    http://imgur.com/xHZKior

  • 9i Form buttons will not click - tab/enter work

    I have created basic forms in 9.0.2 Form Builder.
    The mouse can click the menu items above the form - i.e. close the form, execute query, etc. but none of the buttons on the form are clickable.
    Settings relative:
    Item type: PushButton
    Mouse Navigatable: Yes
    What am I doing wrong/missing?
    I have tried this form, and creating new forms on 3 installations running 9i - none are clickable. I searched back two months worth of messages and the only close match was a 'left/right' click problem - 2 of the installations tried had default right mouse setups.
    Is there a way to run Forms on 9i that are 'not' displayed as web pages - that are displayed like they were in 6.0?
    Thanks,
    Todd Nelson

    Is the Mouse Navigation Limit set at the Form Level (in the Form Property Sheet?)Yes - it says "Mouse Navigation Limit - Form"
    Do the Forms 9i demos work ok? No -
    Tried infobutton - form PJCLAUNCH90 - no mouse...
    insertreplace - form replace90 - also no mouse...
    Of note: the 'buttons' that would have images I imagine - that say '[Roll' in the upper right - don't? Seems like something within the program isn't looking for resources?
    They seem to compile fine - 'Loading Java Applet', Oracle Forms...
    but no mouse support. Have to click on the page then tab to select the 'guessed' upper right close button.
    Could this be a path setup problem - conflict between 9iDS and 9iAS - c:\oracle and c:\orahome1 respectively. What Oracle configuration item relates to how forms find the button image resources?
    Thanks,
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Onmouseover for button images

    I am using images for my buttons. In the attribute section/ image attributes of the button properties I have:
    #APP_IMAGES#addrow1.gif
    I want to change the image when the user mouse over.
    I tried adding: onmouseover="this.src='/i/htmldb/addrow2.gif';" to the image, and copying the image files to the /i/ folder, but it doesn't work. How can I toggle the button image with mouseover?

    hi,
    thanks for reply. How do I post a link do I need to upload it to a server somewhere?
    I sort of got it to work in the end. When I applied onClick or onMouseDown it always applies a second onMouseOver so then I right-click the second onMouseOver in the Beahviors palette and choose onClick from dropdown menu, this seems to fix it.
    Though there is still 1 thing puzzling me. Is it possible to get the onClick image or "hit" button state to restore to original image as soon as user releases mouse button rather than when pointer rolls off the button. Only a very minor detail and not really an issue. Just would look slightly slicker if the "hit" state was a brief flash or pulse.
    cheers
    s

  • Problem with JavaScript in my PDF Form buttons

    I am trying to have my user click on a button in my form on my website and e-mail the form data to me.
    I am using the following JavaScript with my form button:
    this.mailForm(false, "[email protected]", "", "", "Subject", "Message Body");
    Protected mode is off.
    When I use the above statement (whether the 1st parameter is set to true or false), nothing happens – no email gets sent and no mail dialog box appears. If I change from this.mailForm(...) to this.mailDoc(...), I get a mail dialog box but, as expected, it sends the blank form without the filled-in data due to low user privileges.
    How can I send the form data with this.mailForm(...)? (Note that I prefer to use this.mailForm(...) rather than mailto:(...) because this.mailForm(...) supposedly allows me to e-mail the form without user interaction.)
    -- Don

    Thanks for responding.  I have been using “Submit a form” in the Mouse up event.  I had that operation do a mailto: and it worked, but required user interaction on the part of the web page visitor.  I have successfully created an equivalent JavaScript including:
        var url = "mailto:[email protected]?subject=mySubject&body=MyMessage"; 
        this.submitForm(url, true);
    The above sent the FDF file successfully, but again, it required user interaction.
    Then I tried this JavaScript - as I mentioned in a previous post - after you said to use doc.submitForm():
        var url = "http://mydomain.com/submit_notice.php";
        doc.submitForm(url, false);
    The above script seemed to do nothing (with no error message). Shouldn't it bring up the PHP file in the web browser?
    I have that php file, submit_notice.php, created, but I have not written any PHP scripts to e-mail the FDF file.  I have never written a PHP script to take the posted FDF data and email it, but I have used the PHP mail() function and posted variables.
    As for what I want to happen on the client side after the submit takes place: I simply want the FDF file to go to an e-mail that I specify.  Additionally, I need it to happen without any client interaction on the part of the web page visitor.  I can expect that visitor to have Adobe reader, but no add-ons or protected mode requirement.
    Please give me an example that emails the FDF file without any user interaction.
    Thank you.
    -- Don

Maybe you are looking for