I: Headstart 2.1.2, Obsolete Webforms workarounds

Resolved issues in webforms
Headstart for Designer 6.0 and Developer Server 6.0 (patch 5 or higher)
In developer server 6 some issues are resolved where headstart had workarounds for. This document describes the changes that you can apply to
the headstart libraries to remove these workarounds.
1. Show tooltips on the web
In previous developer server versions (before developer 6.0 patch 5), tooltips on the web did not work. As a workaround, tooltips where shown
in the MDI console at the when-new-form-instance. To remove this workaround:
qmsevh50.pll, procedure qms$event_item
Remove the following lines of code:
if qms$help.tooltips_enabled
and qms$application.get_user_interface = 'WEB'
then
qms$item.show_hint;
end if;
qmslib50.pll, package qms$block, procedure init_tooltip
Remove the following lines of code:
if qms$application.get_user_interface = 'WEB'
then
return;
end if;
2. Multiselect SHIFT- and CTRL-click
The problem with multiselect functionality on the web concerned the system variable :system.mouse_button_shift_state. This variable did not
give the right status on the web. The problem can be solved by looking at the variable :system.mouse_button_modifiers. To apply the change,
replace the following procedure in pakage QMS$MSEL:
procedure change_selection
is
l_select_key varchar2(50) := upper(name_in('system.mouse_button_shift_state'));
begin
If (l_select_key = 'SHIFT+'
or g_selection_scope = 'RANGE_SELECT'
and get_range_select_start > 0
Then
SelectRange;
Else
If l_select_key = 'CTRL+'
or g_selection_scope = 'INCREMENTAL_SELECT'
Then
ToggleCurrent;
Else --no interpretable modifier key
If IsSelected
then
unselect_all(name_in('system.cursor_block'));
else
unselect_all(name_in('system.cursor_block'));
SelectCurrent;
end if;
End if;
End if;
exception
when form_trigger_failure then raise;
when others then qms$errors.unhandled_exception('qms$msel.change_selection');
end change_selection;
with this code:
procedure change_selection
is
-- l_select_key varchar2(50) := upper(name_in('system.mouse_button_shift_state'));
-- mva, 05-10-2000 workaround for bug 756682: use mouse_button_modifiers!
l_select_key varchar2(50) := upper(name_in('system.mouse_button_modifiers'));
begin
If (l_select_key = 'SHIFT+'
or g_selection_scope = 'RANGE_SELECT'
and get_range_select_start > 0
Then
SelectRange;
Else
-- If l_select_key = 'CTRL+'
If l_select_key = 'CONTROL+'
or g_selection_scope = 'INCREMENTAL_SELECT'
Then
ToggleCurrent;
Else --no interpretable modifier key
If IsSelected
then
unselect_all(name_in('system.cursor_block'));
else
unselect_all(name_in('system.cursor_block'));
SelectCurrent;
end if;
End if;
End if;
exception
when form_trigger_failure then raise;
when others then qms$errors.unhandled_exception('qms$msel.change_selection');
end change_selection;
null

You mentioned 'the problem with multiselect functionality' but what exactly was the problem? I tried finding the bug 756682 (mentioned in the code) on Metalink but couldn't find it.
Regards,
Edward

Similar Messages

  • Multi-select LOV's hang form and use 100% CPU power

    Hello,
    We are using Designer 6i (6.5.52.1.0) and Headstart 6.5
    In one of our forms we are using 6 Multi-select LOV's.
    When we click the Cancel or Ok button (included through QMS_MSEL_LOV_BUTTONS), or hit Enter query in one of the ML_... blocks the form hangs and starts using all the CPU-power. I've tested this locally (c/s) and through the web (iAS), same result...
    I already rebuilt the LOV's but the problem isn't solved.
    We've got other forms with one or two multi-select LOV's, and these work fine.
    Has anyone experienced this behaviour before, and what is the cure?
    Thanks in advance!
    Wouter

    Wouter,
    If you are running against Solaris, you could be running into the following:
    Headstart applications that run via webforms on a Sun Solaris application server, suffer again from bug 1985903. This bug was spotted and solved a time ago and seemed to be solved at next
    releases of Forms 6i. Now, on Solaris the bug is introduced again.
    Description
    ===========
    1. When using a multi-select LOV (which is displayed in a modal dialog
    window), you select the records you want, press OK, and the application exits.
    2. When using a shuttle control to move records from left to right or vice
    versa, you select the records you want, press '>' to move them, and the
    application exits.
    This occurs in Forms 6.0.8.13.0 and 6.0.8.14.1. It did NOT occur in prior
    releases. This is some kind of forms bug.
    Workaround
    ==========
    For some reason the call to procedure renumber in qms$msel.process_records
    causes the application to exit. If you copy the code from renumber to all the
    places from which it is called, it works fine.
    - open qmslib65.pll in Form Builder
    - open package body qms$msel
    - find procedure process_records and define a local variable l_recno of type
    number.
    - find local procedure renumber and copy the body of this procedure
    (everything
    after 'begin' and before 'exception').
    - replace each call to 'renumber;' with the copied code.
    A new version of qms$msel package body is available on iXchange for download.
    See Headstart Oracle Designer 6i, Bugs and Fixes.
    Hope this helps,
    Marc Vahsen
    Headstart Team
    Oracle NL

  • Displaying detail blocks on tabs within tabs

    Can anyone help with a layout problem? I don't think it can be done with Designer alone, but I was hoping that Headstart could help.
    I have a master block on a new tab page. I want to display 6 records, showing 2 fields as context with the remainder as overflow right in a stacked item group. So far, so good.
    The master block has two detail blocks. I would like to display these as tabs behind the stacked item group from the master table,
    and this is where I run into problems.

    Lynne,
    Unfortunately, this is not supported by Designer and Headstart does not have a simple workaround for this.
    You could try generating the items to stacked canvases and then when the popup page is clicked programatically display the stacked canvas on top of the tabbed canvas. But this is very tricky coding and probably not worth the effort.
    Regards,
    Lauri

  • Headstart V6/8i/NT workaround

    If anyone's interested, I have a workaround for the server bug which gives ORA-03114 on entry to V6 Headstart-generated forms when run against 8i in an NT environment.
    You hit the server bug whenever you have client code which invokes server side procedures using parameters which are either pl/sql records or table of records. Several procedures have such parameters in Headstart's server packages hil_message, qms_message, hil_profile, qms_profile & cg$errors.
    The 1st 4 packages have both parameter types, & are invoked a lot from qmslib50 code, so I copied these packages to qmslib50, renaming them (eg hil2_message, qms2_message etc). All calls to these packages within qmslib50 were changed accordingly. I left cg$errors on the server, but overloaded the procedures which had the pl/sql record parameters (there are no table of records), so that they could be invoked using the constituent items of the pl/sql record. I then changed all calls to these procedures from qmslib50 code.
    Fingers crossed, it seems to be working.

    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Cheryl Riley ([email protected]):
    If anyone's interested, I have a workaround for the server bug which gives ORA-03114 on entry to V6 Headstart-generated forms when run against 8i in an NT environment.
    You hit the server bug whenever you have client code which invokes server side procedures using parameters which are either pl/sql records or table of records. Several procedures have such parameters in Headstart's server packages hil_message, qms_message, hil_profile, qms_profile & cg$errors.
    The 1st 4 packages have both parameter types, & are invoked a lot from qmslib50 code, so I copied these packages to qmslib50, renaming them (eg hil2_message, qms2_message etc). All calls to these packages within qmslib50 were changed accordingly. I left cg$errors on the server, but overloaded the procedures which had the pl/sql record parameters (there are no table of records), so that they could be invoked using the constituent items of the pl/sql record. I then changed all calls to these procedures from qmslib50 code.
    Fingers crossed, it seems to be working.<HR></BLOCKQUOTE>
    null

  • Headstart, webforms on unix

    Hi, I am trying to deploy an application built using headstart on unix
    Is there any know issues and corresponding workarounds to be aware of.
    At this stage we're having a lot of hassle just to copy files across and compiling them.
    There is just no consistency in upper/lower/initcap naming of library/forms/menu files (generated out of designer ofg*.pll) - Has anyone successfully done that.
    Is there any changes to be made to the object library - visual attributes/fonts.
    TIA

    Known UNIX issues for Headstart:
    1. Designer is somewhat inconsistent with uppercase and lowercase attachments in generated modules. :-)
    If you have a lowercase file name on UNIX, but a form or library expects it to be (partly) in uppercase, you can make a
    so-called link. Example: suppose you have a file named qmslib65.pll, but one of your libraries refers to it as
    QMSLIB65.pll. Go to the UNIX folder where you stored qmslib65.pll and perform the following command:
    ln qmslib65.pll QMSLIB65.pll
    After this, you have created a 'synonym' QMSLIB65.pll which points to the real file qmslib65.pll, and the reference
    from your other library will work.
    2. The next issue has to do with translating of registry variables from NT to environment variables in UNIX.
    Headstart has created a few registry entries in a 'Headstart' subdirectory under the Oracle entry.
    HEADSTART\IMAGEFILE_PATH
    HEADSTART\HELPFILE_WEB_PATH
    Unix does not allow environment variables to have a '\' in the name.
    The workaround for this is to move these registry settings up one level to the Oracle node and rename them.
    HSD_IMAGEFILE_PATH
    HSD_HELPFILE_WEB_PATH
    Then, you will need to edit qmslib65.pll and change all references to these variables to the new name.
    3. The final issue occurs in the report launch form.
    QMS0012L.QMS$REPORT must pass the module name in lowercase.
    IF NOT g_module_set
    THEN
    l_module_name := name_in(qms0012f.get_short_name_item);
    -- add lower around l_module_name
    -- because of UNIX !!
    add_par_to_list('MODULE',
    LOWER(l_module_name));
    END IF;
    Regards,
    Lauri

  • Need Workaround for periodical autocommit in WebForms without using Timer

    Hi guys...
    I need to use autocommit in my form for say 1 min.
    As ther is a great performance degradation when i go for timers, i need a workaround to achieve the same functionality without using timers.
    Thanx & Regards
    Sriram

    <p>Get this zip file
    <br><br>
    unzip the file<br>
    copy the bean_timer.jar in your <forms_home>/java directory<br>
    update your formsweb.cfg configuration file<br>
    archive_jini=f90all_jinit.jar,...,bean_timer.jar<br><br>
    open, compile and run the beantimer.fmb sample demo
    <br>
    </p>
    Francois

  • Headstart prevents using Module components based on IOTs

    I want to build a module component based on an index-organized
    table. The following Designer + Headstart behaviour prevents
    correct functioning of such a block:
    - Block property 'Enforce Primary Key' must be set
    - Block Property 'Key mode' must be set to 'Non Updatable'
    - 'Primary Key' property of PK items must be set
    - The event ON-LOCK calls qms$record.unlock, which calls
    the lock_record built-in. This should not be done for an IOT.
    Solutions:
    - I have made new source objects for IOT Block and PK items,
    and assign these to the MC and bound items when applicable.
    - I modified the ON-LOCK event to not include the lock_record.
    The qms$record.unlock procedure is obsolete anyhow, since it
    is a workaround for an old (solved) bug.
    Headstart Team:
    I recommend you include these workarounds in the standard object
    library and pl/sql library.

    Peter,
    Thanks for your feedback. I have posted an enhancement request
    for the next release of Headstart.
    Regards,
    Lauri

  • Headstart 6i - no client/server support?

    Hello,
    I have received today list of some new features of Headstart 6i (Beta supposed to be available this week).
    In the new features list, here what it is wrote:
    <<Because of known issues associated with running Forms 6i in a client-server environment, Headstart 6i will not be certified for client-server deployment. Applications can still be deployed client-server, but Headstart will not attempt to identify and overcome client-server specific issues.>>
    Is someone have heard about these "known issues" in client/server?
    Thank you
    Jean
    null

    The problems are GUI issues.
    The basic problem is this:
    Headstart can either be optimized to display in Webforms with the Oracle Look and Feel, or it can be optimized to display in client-server mode. You can't do both at the same time. Since we had to pick one or the other, we chose the Webforms OLAF GUI settings.
    You can customize the template package to revert to the client-server GUI settings if you like. This basically involves changes to the visual attributes in the object library, removing the use of the keyword 'automatic' and setting actual colors for foreground color, background color and fill pattern.
    There are also problems with displaying the menu and Smartbar. You should remove the icons that are displayed in the menu. If an entire menu group is disabled, the associated icons on the Smartbar disappear instead of greying out (no workaround).
    There might also be other GUI issues. As stated, we have not tried to identify or resolve these issues.
    Regards,
    Lauri

  • Upgrading to Headstart Ruleframe

    At the moment we have several applications running. Some have been build using
    Headstart Desinger/2000, while others have been build using Headstart
    Ruleframe.
    Of course, because of this we have to maintain both versions of Headstart. We
    would like to use only one version of headstart, Headstart Ruleframe.
    Is there any information on how to easily migrate the applications using Headstart
    Designer/2000 to Headstart Ruleframe?
    Is it possible to regenerate an application replacing Headstart Designer templates and libraries with those of Headstart Ruleframe?
    Which steps are involved?
    Appreciate your help!
    null

    Matthijs,
    Yes, it is possible to migrate the Headstart software to the new versions (i.e. patch 12) without really starting to use CDM RuleFrame.
    In each form that will be recompiled after you upgraded Headstart to patch 12, there will be a call to qms_transaction_mgt.open_transaction and close_transaction. So these packages should be installed but because no business rules are put on the rule stack (TAPI does not call CAPI package), the close_transaction will always succeed.
    Notice that several utilities will be disabled after installation of CDM RuleFrame (e.g. the utility to workaround the Mutating Table problem, which has become obsolete as soon as you start using CDM RuleFrame).
    Kind Regards, Marc

  • Designer6.0/Headstart to Designer 9i

    Hello world,
    Is it possible to use the Designer 6.0-Headstart version (qmsolb50, qmstpl50 etc) in combination with Designer 9i? Is it possible to migrate from Designer 6.0 to 9i without upgrading Headstart (I know a recompile in Developer 9i is needed, but should I buy the 9i-version)?
    Are there any known limitations, bugs, workarounds etc?
    TIA
    Roel Hartman

    Roel,
    As designer9i and designer6i (at the moment) hardly differ, what you intend to do resembles strongly a 'simple upgrade' strategy from designer 6.0 to
    designer 6i.
    Main difference is that you need the headstart designer 9i software (up to 6.5.3.1 available through the supplement option). Just follow the instructions in miggd65.pdf, chapter 2 and 3.
    There are of course known limitations of using the simple upgrade strategy, the migration guide explains in detail when to choose for simple, when to choose for a full upgrade scenario.
    My advice would be to always full upgrade an application, unless no functionality changes are to be expected anymore.
    Mind that the headstart templates for designer 6i intend to fully exploit webforms functionality and new designer 6i features.
    For more information on this, refer to the release notes (relhsd65.htm) and the migration guide mentioned above, both included in the iDevelopment Accelerators software suite.
    Regards, Marc
    Headstart Team

  • Custom forms (with Headstart), issues.  Prompted more than once to save/commit.

    We have found that after analyzing the APPS schema (for CBO), we
    have an issue with custom forms. This issue relates to an
    earlier post on this forum where we get prompted several times
    to save/commit our changes and that the changes are never
    submitted. We've narrowed it down to the QMS_TRANSACTIONS
    table, when ever we run...
    analyze table apps.QMS_TRANSACTIONS estimate statistics;
    Table analyzed.
    Our custom forms will stop working. Why is this? So far we've
    found the only work around is to drop all Headstart objects and
    run the scripts to recreate the objects in the APPS schema.

    Michael,
    This might be a similar problem as they have experienced in
    Japan. Their problem description is as follows;
    -At the beginning, the transaction can be committed from the
    screen.
    -After analyzing APPS schema, it becomes impossible to commit the
    transaction.
    This problem is reproduceable in following condition;
    -Use Oracle 8i 8.1.7.x.
    -Set '_push_join_union_view' parameter to true. (Set by Rapid
    Installer of EBS)
    -Analyze the schema that has qms_transactions table.
    This problem seems to be caused by DB bug (Bug no 2058756).
    If this is indeed your problem a workaround has been described to
    set the event 10195 before analyzing the table.
    Hope this helps.
    Regards,
    Sigrid Gylseth.

  • Webforms visible in project view but not in browser view

    Hi all
    I have a problem:
    We have a Yearly Task list with several webforms. Now, if I try to open the webforms in the normal project view everything works fine. But if I click the same Webform when I am in the browser view/tasklists/Yearly, I get the following Error message.
    Requested document does not exist.
    Show Details:
    Error Reference Number: {A9C8569B-EC64-4A6D-8FEB-897DA44ECF5C};User Name: 20354@MSAD
    Num: 0x80042781;Type: 0;DTime: 02.02.2009 11:58:29;Svr: ZRHCHL60;File: CHsvDSReports.cpp;Line: 626;Ver: 9.3.1.0.1502;
    Num: 0x80042781;Type: 0;DTime: 02.02.2009 11:58:29;Svr: ZRHCHL60;File: CHsvReports.cpp;Line: 1538;Ver: 9.3.1.0.1502;
    Num: 0x80042781;Type: 0;DTime: 02.02.2009 11:58:29;Svr: ZRHCHL60;File: CHsvReports.cpp;Line: 1081;Ver: 9.3.1.0.1502;
    Num: 0x80042781;Type: 0;DTime: 02.02.2009 11:58:29;Svr: ZRHCHE62;File: CHFMwManageDocuments.cpp;Line: 1340;Ver: 9.3.1.0.1502;
    Strangely, this only happens with the webforms that I have added more recently. The older webforms work fine also in the browser view.
    Thanks

    Hi all,
    We try to import Webforms from an application in a new application , inside a folder hierarchy.
    There was the same error when we want to access to any documents.
    The folder was created by an Active Directory User (With All rights).
    I have created a Folder with a Native Account (With All Rights) , and access to the document is now available.
    I hope this workaround, will help Oracle to understand the root cause.
    Regards.

  • Closing Application - Headstart bug?

    This mail was originally posted on the ODTUG maillist.
    I am using Headstart Qms 5.0 and we are having problems with closing the
    application window using the Windows Close button[x]. Detailed description
    follows:
    When window is closed by pressing the 'x' found at the right topmost part of
    the screen, a message appears confirming whether to commit, not commit or
    cancel changes. Once cancel button is pressed, it creates infinite loop or
    sometimes shows the same message several times.
    The temporary workaround was to comment out the before code added by QMS in
    the key-exit trigger: qms$event_form('KEY-EXIT');
    /* CGAP$TES_SEQUENCE_BEFORE */
    /*begin
    qms$event_form('KEY-EXIT');
    end; */
    /* CGNV$CLOSE_ALL_WINDOWS */
    BEGIN
    CGNV$.nav_enter_query := FALSE;
    IF (:SYSTEM.MODE = 'ENTER-QUERY') THEN
    exit_form;
    ELSE
    CGNV$.CLOSE_ALL_WINDOWS;
    END IF;
    END;
    /* CGAP$TES_SEQUENCE_AFTER */
    begin
    qms$event_form('KEY-EXIT','AFTER');
    end;
    Although this solves the problem of infinite loop, this needs to be further
    investigated because the code is actually handling the case where system
    mode is 'ENTER-QUERY':
    procedure close_current is
    -- Purpose: Exit form, regardless of form mode
    begin
    -- Cancel query mode when running in query mode, and then
    -- perform do_key('exit_form') as OFG generates code in KEY-EXIT trigger
    to close
    -- child forms when preference NAVCCF is set to Yes
    do_key('cancel_query');
    if name_in('system.mode') = 'ENTER-QUERY'
    then
    copy('10','system.message_level');
    exit_form;
    copy('0','system.message_level');
    end if;
    g_closing_current := true;
    do_key('exit_form');
    exception
    when form_trigger_failure then raise;
    when others then
    qms$errors.unhandled_exception('qms$form.close_current');
    end close_current;
    Looks like a Qms bug to me. Is anyone familiar with this? All help highly
    appreciated.
    Rgds,
    Siggi

    This reply was originally posted on the ODTUG maillist.
    I ran into this problem. It was a Forms 5.x bug. It was definitely fixed
    in 6.0. I can't remember the patch set in 5.0 that fixed it. It was not a
    Headstart problem, but rather a Forms bug.
    Mari Cobb
    Oracle Certified Professional
    Independent Consultant
    Sacramento, California www.ms-mari.com
    null

  • Has anyone fixed the Headstart libraries for Forms 11 ?

    I have a 100% generated Designer - Forms application using the %65.pll headstart libraries - the so-called Headstart version 6.5i.
    Currently our production environment is running on Oracle Application Server 10.1.2. It works fine, however, because of several reasons (the underlying Oracle Portal environment is not working properly anymore on Internet Explorer 10) and continuous alerts that our customers may not use Java 6 and should upgrade to Java 7, we have to migrate to 11g.
    We have installed Fusion Middleware 11.1.1.6, upgraded Portal and recompiled all Forms modules and libraries. Also the Headstart libraries compiled ok. However, when we start a form we get the message that it has been created with an older version of Forms and it quits.
    The consequence is that i have to migrate the Forms as well with the tool frmplsqlconv. Sadly that fails on the Headstart libraries. For example these errors occur:
    CG$MESSAGE: The String CALL was found. If it is an occurrence of the Forms Built-In, It should be replaced with CALL_FORM.
    CG$_SHOW_KEYS: MENU_SHOW_KEYS changed to SHOW_KEYS
    CG$_PREVIOUS_MENU: The PREVIOUS_MENU Built-in is obsolete and will not compile.
    CG$_HELP: The MENU_HELP Built-in is obsolete and will not compile.
    CG$_EXIT: The EXIT_MENU Built-in is obsolete and will not compile.
    CGNV$FIRST_NAV_ITEM: BREAK changed to DEBUG.SUSPEND
    Does anyone have Headstart libraries with fixes for these errors?

    Hello Mark,
    the problem has been fixed...
    1) I tried to migrate the forms to 11g, but that can not be done with headstart... The fmb/pll files should be kept on 10g.
    2) The migration documentation is not complete: webutil has been installed completely (in other words, webutil is not migrated)
    So, steps are:
    1) Install webutil
    2) Recompile all libraries (including headstart and webutil)
    3) Recompile all menus
    4) Recompile all forms
    Then the Forms application works again.
    Java 7 update 21 is very dramatic. The "vendor" work-around can not be used anymore, like with previous Java 7 versions... It is unbelievable how amateuristic Oracle deals with Java. For me, Java in the client is dead as long as Oracle has the controls. So, the end of Forms is very near. If you are also looking for alternatives, check theformspider.com.
    Thanks for your help.
    Best regards, Jan Willem Vermeer

  • RMAN-06207 when DELETE NOPROMPT OBSOLETE;

    Hello all
    I want to backup and delete backuped archivelogs on a standby instance using the following script:
    RUN
    ALLOCATE CHANNEL ch1 DEVICE TYPE sbt PARMS='ENV=......';
    BACKUP ARCHIVELOG ALL DELETE INPUT;
    DELETE NOPROMPT OBSOLETE;
    RELEASE CHANNEL ch1;
    When deleting all obsolete backup pieces, I receive the following error:
    RMAN-06207: WARNING: 1 objects could not be deleted for SBT_TAPE channel(s) due
    RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
    RMAN-06210: List of Mismatched objects
    RMAN-06211: ==========================
    RMAN-06212: Object Type Filename/Handle
    RMAN-06214: Backup Piece c-2414804385-20080820-02
    As a workaround, I then manually delete obsolete backup pieces using:
    delete force noprompt obsolete device type sbt_tape
    What is the cause for rman-06207 ? How can I change my rman script to safely delete backuped archivelogs?
    I work with Oracle 10G release 10.2.0.3 both on standby and catalog DB.
    Casi

    Did you try using the CROSSCHECK command to verify the backup files status?
    From your comments, it doesn't seem like you did. CROSSCHECK checks the status of the RMAN backups against the disk/tape and updates the RMAN repository. CROSSCHECK does not remove any files just updates the status. The status options are - expired, available, and unavailable.

Maybe you are looking for

  • Transferring an app (no longer in appstore/on PC) from iPad to iPhone - help please

    I have a bit of a problem. I have an app on my iPad which I also want to put on my iPhone. I, nowadays, sync via iCloud. This is the situation: 1. The app no longer exists in the app store. I do have the app on my iPad. 2. I do no longer have the app

  • Incorrect text size in Adobe Photoshop CS5 for Mac?

    Hey all, I am posting this for an older gentleman who is a photographer and uses Photoshop on his Mac. His iMac runs OSX 10.9.3 and he uses version 12.0.4 X64 of Photoshop CS5. I noticed when I was to his place the other day giving him tutoring sessi

  • Is there any support for JDBC

    Hey All, I've started working JDBC since few days and already had early hiccups !!! I installed Oracle * into my PC and wrote a simple code to connect to the database unfortunately it didn't connect Now I am not sure whether there is any support for

  • Selection screen in program RLLQ0200

    Hi all. I am trying to launch RLLQ0200 for movement 411K to transer material in consigment into own. I want to transfer the stock in storage type 100 and bin PROD. Once the data is selected I can display some materials but some of them can not be sel

  • Expandable Sections or pages in LiveCycle, best solution

    I have a form that needs tweaking.  I need to be able to add additional info for certain sections of the form if need be.  I am not sure the best way to  go about without adding a extra page that may get printed sometimes that could be blank.   I als