Error Dynpro_not_found

using this code to call me22 but getting error dynpro_not_found
FORM transaction_bdc .
  DATA :
  wf_number type i,
  wf_trans type i,
  v_cnt(2) TYPE n,
  v_bst(2) TYPE n,
  v_bn TYPE i,
  v_bstpo(25),
  v_ebtyp(25),
  v_menge(25),
  v_eeind(25),
  v_xblnr(25),
  v_xblnr1(25),
  v_ebelp(2) TYPE n,
  v_ebelpt(2),
  v_menge1(11),
  v_ebt TYPE i,
  v_vebtyp LIKE ekes-ebtyp,
  v_eb(2) TYPE n,
  v_tcselflag(40),
  v_tem(2) TYPE n,
  v_correct TYPE i,
  v_file TYPE string.
  DATA: ls_outtab TYPE tb_struc.
  DATA: l_valid TYPE c,
        l_locked TYPE c.
  CALL METHOD g_grid->check_changed_data
    IMPORTING
      e_valid = l_valid.
  IF l_valid EQ 'X'.
    LOOP AT tb_output WHERE check EQ 'X' .
      MOVE-CORRESPONDING tb_output TO itab_output.
      APPEND itab_output.
      CLEAR itab_output.
    ENDLOOP.
    IF tb_output-check <> 'X'.
      MESSAGE e003 WITH text-004.
    ENDIF.
  ENDIF.
  loop at itab_output.
  if sy-subrc = 0.
  v_bst = v_bn + 1.
  else.
   v_bn = v_bn + 1.
   endif.
endloop.
  IF itab_output[] IS NOT INITIAL.
    PERFORM open_group.
***looping at purchase order level.
    LOOP AT itab_output .
*read table itab_output with key ebelp = ekpo-ebelp.
      CLEAR v_bn.
      CLEAR v_ebt.
      PERFORM bdc_dynpro USING 'SAPMM06E' '0105'.
      PERFORM bdc_field USING 'BDC_CURSOR'
      'RM06E-BSTNR'.
      PERFORM bdc_field USING 'BDC_OKCODE'
      '/00'.
      PERFORM bdc_field USING 'RM06E-BSTNR'
      itab_output-ebeln.
***Changing alphanumeric fields and quantity fields to character type**
v_ebelp = itab_OUTPUT-ebelp.
clear v_ebelpt.
v_menge1 = itab_OUTPUT-menge.
v_ebelpt = v_ebelp.
***End Of Changing**
*Checking for the exact number of the item**
     LOOP AT itab_output where ebeln = tb_output-ebeln.
       IF tb_output-ebelp = itab_output-ebelp.
         exit.
       ELSE.
         v_bn = v_bn + 1.
       ENDIF.
     ENDLOOP.
*v_bst = v_bn + 1.
*End Of Checking**
**Mapping items**
        v_tem = 1.
        CONCATENATE 'RM06E-BSTPO(' v_bst ')' INTO v_bstpo.
        CONCATENATE 'RM06E-TCSELFLAG(' v_tem ')' INTO v_tcselflag.
        PERFORM bdc_dynpro USING 'SAPMM06E' '0120'.
        perform bdc_dynpro using 'SAPLMEGUI' '0014'.
        PERFORM bdc_field USING 'BDC_CURSOR'
        v_bstpo.
        PERFORM bdc_field USING 'BDC_OKCODE'
        '=DETA'.
        PERFORM bdc_field USING 'RM06E-EBELP'
        v_ebelpt.
       itab_output-ebelp.
        PERFORM bdc_dynpro USING 'SAPMM06E' '0111'.
perform bdc_dynpro using 'SAPLMEGUI' '0014'.
        PERFORM bdc_field USING 'BDC_CURSOR'
        'EKPO-BSTAE'.
        PERFORM bdc_field USING 'BDC_OKCODE'
        '/00'.
        PERFORM bdc_dynpro USING 'SAPMM06E' '0120'.
perform bdc_dynpro using 'SAPLMEGUI' '0014'.
       PERFORM bdc_field USING 'BDC_CURSOR'
       v_bstpo.
        PERFORM bdc_field USING 'BDC_OKCODE'
        '=BSTA'.
        PERFORM bdc_field USING 'RM06E-EBELP'
        v_ebelpt.
       itab_output-ebelp.
        PERFORM bdc_field USING v_tcselflag
        'X'.
**Checking weather Confirmation category already exists**
        SELECT ebtyp FROM ekes INTO v_vebtyp WHERE ebelp =
        itab_output-ebelp AND ebeln = itab_output-ebeln.
        ENDSELECT.
        IF sy-dbcnt > 0.
          v_ebt = sy-dbcnt.
        ENDIF.
        v_eb = v_ebt + 1.
**End Of Checking**
**For Line items**
        CONCATENATE 'EKES-EBTYP(' v_eb ')' INTO v_ebtyp.
        CONCATENATE 'EKES-MENGE(' v_eb ')' INTO v_menge.
        CONCATENATE 'RM06E-EEIND(' v_eb ')' INTO v_eeind.
        CONCATENATE 'EKES-XBLNR(' v_eb ')' INTO v_xblnr.
*End**
        PERFORM bdc_dynpro USING 'SAPLEINB' '0200'.
perform bdc_dynpro using 'SAPLMEGUI' '0014'.
        PERFORM bdc_field USING 'BDC_CURSOR'
        v_xblnr.
        PERFORM bdc_field USING 'BDC_OKCODE'
        '=BU'.
        PERFORM bdc_field USING v_ebtyp
       itab_output-ebtyp.
        PERFORM bdc_field USING v_eeind
        itab_output-eindt.
        PERFORM bdc_field USING v_menge
         v_menge1.
       itab_output-menge.
        PERFORM bdc_field USING v_xblnr
        itab_output-xblnr.
wf_number = 0.
**End Of Mappings**
*loop at itab_output.
        MOVE-CORRESPONDING itab_output TO ekes.
        modify ekes.
        wf_number = wf_number + 1.
       MOVE-CORRESPONDING itab_output TO eket.
       MODIFY eket.
       MOVE-CORRESPONDING tb_output TO ekpo.
       MODIFY ekpo.
*endloop.
endloop.
     endif.
wf_trans = 0.
       CALL TRANSACTION 'ME22'
       USING itbdc
       MODE   'A'.
wf_trans = wf_trans + 1.
*perform bdc_transaction using 'ME22N'.
**End Of Purchase Order Loop**
    PERFORM close_group.
ELSE.
   MESSAGE i083(zv).
ENDIF.
ENDFORM.                    " TRANSACTION_BDC

HI ,
  This basically means that one of the screen number you have entered in the BDC table does not exist , to get the exact error again run the BDC in mode 'A'.
Regards
Arun

Similar Messages

  • Runtime Error DYNPRO_NOT_FOUND after transport of customer subscreen

    Hi,
    We have created a new customer subscreen 9002 using transaction OXK1. When the subscreen was transported to the quality system, the subscreen was not generated thereby causing a dump (error DYNPRO_NOT_FOUND) in transaction FB01 which was using the subscreen.
    Are customer subscreens not regenerated automatically when they are transported?
    Thanks.
    Ekit

    HEllo,
    Sometimes error happen in this process. Please re-generate your scrren.
    goto  OXK1 Select the screen and go to the menu option Subscreen -> Generate.  
    REgards,
    REnan Correa

  • Error DYNPRO_NOT_FOUND in MIGO

    Hi,
    Error DYNPRO_NOT_FOUND occurs at Goods Receipt in MIGO , for a particular production order and clicking on Classification tab to create a batch.
    The error indicates that the screen 900 of the program SAPLXVBZ does not exist.
    Awaiting valuable inputs.
    Thanks in advance.
    Neethu

    Hi
    SAPLXVBZ is main program of function group XVBZ, here there are defined many user-exit: probably there's a statament CALL SCREEN 900 in one of this exit, but nobody has defined that screen.
    U should find out in which exit that screen is called and delete that line or create the screen (but it's not really good call a screen or popup in a exit).
    Max

  • Runtime Errors   DYNPRO_NOT_FOUND

    Hi,
    While running TCode ME21N we are getting the below mentioned Dump:We are on ECC 5.0 and the latest Support Pack.
    Runtime Errors         DYNPRO_NOT_FOUND
    Date and Time          11.12.2008 12:46:17
    ShrtText
         Screen does not exist
    What happened?
         Error in ABAP application program.
         The current ABAP program "RM_MEPO_GUI" had to be terminated because one of the
         statements could not be executed.
         This is probably due to an error in the ABAP program.
         The program had to be terminated.
    Error analysis
        Program "RM_MEPO_GUI" tried to use screen 1000.
         The screen does not exist.
    Trigger Location of Runtime Error
         Program                                 RM_MEPO_GUI
         Module Name                             SYSTEM-EXIT

    Hi Nitin,
    Kindly, please let me know how did you solve this issue.
    I have the same issue, where i am getting the DYNPRO_NOT_FOUND error while executing the SAPLMEGUI(ME21N).
    Error - SAPLMEGUI program tried to access screen 0120 which is not exist.
    Kindly recollect and help me how did you solve this problem.
    Thanks,
    Bharath.

  • Runtime error DYNPRO_NOT_FOUND when creating business entity in SAP RE-FX

    Hello,
    I have a problem...
    In SAP RE-FX (Real Estate) when I try to do the most basic thing like creating a business entity (transaction REBDBE), I get a runtime error 'DYNPRO_NOT_FOUND'.
      Program                                SAPLBUSS
      Include                                  LBUSSO00
      Row                                     1.543
      Module type                          (MODULE PBO)
      Module Name                         PBO_START_SUBSCREEN
    Does anybody know how I can fix this?
    Thanks in advance!

    Hi
    look OSS Note [162119|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3136323131313926] note youe need to have market place login
    1621119 - Dump DYNPRO_NOT_FOUND in SAPLBUSS in module PBO_START_SUBSCREEN
    Regards,
    koolspy.

  • Trans QA12  ERROR:DYNPRO_NOT_FOUND

    I create quality notification by using trans qm01 then I assign task to it and release both (notification and the task) 
    I can see and work on the task (i.e. change its status to complete) through trans qm02 .
    but when I want to work on the task using trans. QM12 I see the tasks list but when i choose one line (task)  and push on the task button I get  ABAP runtime errors    DYNPRO_NOT_FOUND
    I will appreciate yours help
    Eyal Rosenfeld

    Hi,
    First verify your Customizing of Notification Tabs.If every thing is OK.Then it could be source code problem.Pl. look for SAP notes.I checked for QM12 T.code there is a note very relevent for DYNPRO_NOT_FOUND problem.Pl. check
    Regards
    Mathi

  • Runtime error Dynpro_not_found

    Hi experts,
    I get the following runtime error when trying to open a Z table under SM30.
    Short text                        
         Dynpro does not exist         
    Error analysis                                                            
        The system attempted to use dynpro 0100 in program "SAPLZGET_ORG".    
        This dynpro does not exist.                                                                               
    User and Transaction                                                                               
    Client.............. 100                                                                     
        User................ "ARUN"                                                                  
        Language key........ "E"                                                                     
        Transaction......... "SM30 "                                                                 
        Transactions ID..... "4976D21BC7F841F0E1000000C0A80046"                                                                               
    Program............. "SAPLZGET_ORG"                                                          
        Screen.............. " "                                                                     
        Screen line......... 0                                                                       
    Line  SourceCde                                                                               
    97             i_messnbr = '288'.                                                              
       98           ELSE.                        "customer system                                     
       99             i_messnbr = '289'.                                                              
      100           ENDIF.                                                                               
    101         ENDIF.                                                                               
    102         MESSAGE ID 'AM' TYPE 'I' NUMBER i_messnbr                                           
      103                         WITH vim_addr_basetable                                             
      104                              vim_addr_bastab_field                                          
      105                              vim_tsadrv-tablename                                           
      106                              vim_tsadrv-fieldname.                                          
      107         CLEAR x_header-adrnbrflag. MODIFY x_header INDEX 1.                                 
      108       ELSE.                            "entry in TSADRV is complete                         
      109         vim_addr_group = vim_tsadrv-addr_group.                                             
      110         IF x_header-adrnbrflag EQ 'O'.                                                      
      111           CALL FUNCTION 'ADDR_GET_STATUS_INFO'                                              
      112             TABLES                                                                          
      113               status_table = i_statetab.                                                    
      114           READ TABLE i_statetab WITH KEY                                                    
      115                constant = vim_tsadrv-addr_group.                                            
      116           IF sy-subrc NE 0. CLEAR i_statetab-value. ENDIF.                                  
      117           TRANSLATE i_statetab-value USING ' OXN'.                                          
      118           x_header-adrnbrflag = i_statetab-value.                                           
      119           MODIFY x_header INDEX 1.                                                          
      120         ENDIF.                                                                               
    121       ENDIF.                                                                               
    122     ENDIF.                                                                               
    123   ENDIF.                                                                               
    124   PERFORM vim_process_assigns.                                                              
    125   IF <status>-initializd EQ space.     "not processed yet               
    126 * reset dropdown lists                                                  
    >>>     CALL FUNCTION 'VRM_REFRESH_VALUES'.                                 
    128     IF x_header-frm_af_ini NE space.   "user exit exists AND            
    129 * set environment for user exit.                                        
    130       ASSIGN dba_sellist-sys TO <vim_sellist>.                        
    131       vim_enqueue_range = x_header-subsetflag. assigned = 'X'.          
    132 * perform user exit -> 3.0B processed in JUSTIFY_ACTION_MODE            
    133       PERFORM (x_header-frm_af_ini) IN PROGRAM (sy-repid).              
    134     ENDIF.                                                              
    135 * backup DBA_SELLIST                                                    
    136 *    REFRESH vim_dba_sel_kept.                        "UF210200b        
    137 *    APPEND LINES OF dba_sellist TO vim_dba_sel_kept.                   
    138 * remove multiple values for subsets                                    
    139     DELETE dba_sellist WHERE ddic = 'M'.                                
    140     DESCRIBE TABLE dba_sellist.                                         
    141     IF sy-tfill GT 0.                                                   
    142       READ TABLE dba_sellist INDEX sy-tfill.                            
    143       CLEAR dba_sellist-and_or.                                         
    144       MODIFY dba_sellist INDEX sy-tabix.                                
    145     ENDIF.                                                  "UF210200e  
    146   ENDIF.                                                                               
    Please kindly help me out with the issue.
    Thank You.

    Hi,
    What is the screen number given when you created the maitenence generator? Over here it seems it is trying to open the table in sm30 using screen 0100.
    Try to recreate the table maintenence generator. Delete the existing maintenence generator and when screen number is there select propose screen number so the system suggests the screen number.
    Then try to maintain entries via sm30.
    Hope this helps.
    Regards,
    Sachin

  • CATT Recording Error with ME32 / ME32L (DYNPRO_NOT_FOUND)

    Hello,
    I am trying to record a CATT test case with transaction ME32 or ME32L and am failing when I go into the "Header Details" section.  I am trying this on a IDES 4.6c system.
    The error I receive is "Runtime error DYNPRO_NOT_FOUND has occurred".
    Please help.  Not sure what to do.
    Thanks,
    Charles

    Hi,
    Check is there any screen exit which might getting triggered with set values your passing to the Bapi.
    as cannot handle z screens which are added to the traansaction.
    Check whether it happening for all set of data or not ...if not check for the what values it is giving dump.

  • ABAP runtime error in FBV2 Change parked document using workflow

    Hi,
    When selecting screen template variant in tcode FBV2 change parked document, I get abap runtime error DYNPRO_NOT_FOUND
    Tcode- FBV2
    Program- SAPLF040
    Screen- SAPLF040  0310
    Main Program - SAPMF05V
    Information on were terminated.
    Program SAPLF040 - in " %_CTL_END "
    In the source code you have the termination point in line 50 of the (Include) program " <SYSINI> "
    How can we solve this error. We are on ECC6 with release 600.
    Thanks,
    Mark

    Hi Mark,
    We have this same issue in transaction F-65
    I believe that when a new screen template is configured, a new screen is generated within function group F040. A later action (applying a hotpack??) has removed this screen, but the config (in table T021D) still points the processing to the screen even though it has been removed.
    Did you find a solution? We want to get the screen back as it is still valid to use this screen template in the business
    Thanks
    Ben

  • Error while clicking on WBS in CJ20N

    Hi,
    When i run CJ20N and click on WBS element it giving me dump saying -
    Runtime Errors         DYNPRO_NOT_FOUND
    ShrtText
         Screen does not exist
    What happened?
         Error in ABAP application program.
         The current ABAP program "SAPLCSCR" had to be terminated because one of the
         statements could not be executed.
         This is probably due to an error in the ABAP program.
         The program had to be terminated.
    Error analysis
         Program " " tried to use screen 0000.
         The screen does not exist.
    Trigger Location of Runtime Error
         Program                                 SAPLCSCR
         Module Name                             SYSTEM-EXIT
    What should be done for this and which points should i consider to solve this?
    Pls. help.

    HI,
    I checked all the exits u have mentioned but none of them were implemented.
    What can i do now?

  • DYNPRO_NOT_FOUND : ABAP program "MP058400"

    Dear Sir
    Category ABAP Programming Error
    Runtime Errors DYNPRO_NOT_FOUND
    ABAP Program MP058400
    Application Component PA-PA-IN
    Dynpro does not exist.
    The system attempted to use dynpro 0000 in program "MP058400".
    This dynpro does not exist.
    Kindly help for this
    Regards
    HARISH.B

    Whether you have enhanced the code, any new customization lately?

  • Dynpro_not_found ML81N

    the scenario: Once user exit project Z1(package is $TMP). It contains one enhancement assignment Z2. Z2 has some user's customized codes. Z2 is active and then saved in one change request and last it is sent to PRD and it can work. This sounds some strange but please temptly neglect it. Z2 is one user exit of T-code ML81N.
    To avoid some unexpected issues, I want to chagne Z1's package from $TMP to one that can be sent to PRD. So I deleted Z1 and then created project Z3. Its package is zazpc which can be sent to PRD. Then put Z2 into Z3, active Z3, then I have get the dump information when I run ML81N.
    The dump information is below. But I didn't create any screen in the user exit. I just put input some codes in the enhancement 'SRVESSR'.
    "Runtime Errors         DYNPRO_NOT_FOUND
           Occurred on     09/11/2009 at 15:57:14
    Screen does not exist
    What happened?
    Error in ABAP application program.
    The current ABAP program "SAPLMLSR " had to be terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    The program had to be terminated.
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    Error analysis
    Program "SAPLXMLU" tried to use screen 0399.
    The screen does not exist.
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:"

    Hi Ganjian,
    first of all you have to find out where the screen call is issued.
    In Include LMLSRF1B, set a break-point before and after CALL CUSTOMER-FUNCTION '001' (line 50) and check if really comes from your user exit. In the dump, you can also see the Active Calls/Events section to find out more.
    As your dump says
    Program "SAPLXMLU" tried to use screen 0399.
    it might be possible that your user exit does more than you are aware of.
    Also possibly someone already used the new ENHANCEMENT FRAMEWORK to insert code at some SPOT.
    Regards,
    Clemens

  • DYNPRO NOT FOUND - Runtime Error

    A run time error "DYNPRO_NOT_FOUND" occurred while the ABAP program "SAPLCV130" was terminated.
    Error Analysis reports that system attempted to use dynpro 1231 in program "SAPLCV130" where in the dynpro did not exist.
    Can you provide us the options and how to proceed on with it.

    Hi,
    Kindly try running transaction BUSP.
    Thanks and warm regards,
    Tapan.

  • DYNPRO_NOT_FOUND  in abap program dumps in st22

    Hi All,
    We are  facing an issue in Abap dumps
    Run Time error  DYNPRO_NOT_FOUND
    Termination occurred in the ABAP program "MP058400" - in "SET_INIT_TAB".
    The main program was "MP058400 ".
    In the source code you have the termination point in line 49
    of the (Include) program "MP058420".
    I have an idea that it is releated to Screens but  its a standard Tcode PA40  and info type 584.
    Please suggest the how can i solve the dump.
    Regards
    Harsha Teja

    Hi Deepak,
    We had installed ECC 6.0 Ehp5  recently and released to HCM consultant  they are testing PA30 infotype 584.
    Regrads
    Harsha Teja

  • BAPI_SALESORDER_CHANGE - dynpro_not_found ???

    Dear all,
    I found a lot of discussions about using BAPI_SALESORDER_CHANGE and possible errors, but I didn't find anything about the runtime error 'DYNPRO_NOT_FOUND' ...
    As may other developers I want to change 'reason for rejection', but when the BAPI is executing, I get a dump with the error 'dynpro not found' ... I have no idea why I get this error ...
    The program I wrote is :
    report zsd_settlebulkorders.
    tables: vbak, vbap, vbup.
    data: begin of gt_items occurs 0,
             vbeln      like vbak-vbeln,
             posnr      like vbap-posnr.
    data: end of gt_items.
    data: gt_orditems  type bapisditm  occurs 0 with header line.
    data: gt_orditemsx type bapisditmx occurs 0 with header line.
    data: gt_return    type bapiret2   occurs 0 with header line.
    data: gs_ordhead   type bapisdh1.
    data: gs_ordheadx  type bapisdh1x.
    data: gv_vbeln     type bapivbeln-vbeln.
    select-options: s_vbeln for vbak-vbeln.
    start-of-selection.
    refresh: gt_items.
    select vbap~vbeln vbap~posnr into table gt_items from vbap
                                                                                    inner join vbak
                                                                                    on vbak~vbeln = vbap~vbeln
                                                                                    inner join vbup
                                                                                    on vbup~vbeln = vbap~vbeln
                                                                                    and vbup~posnr = vbap~posnr
                                                                                    where vbak~vbeln in s_vbeln
                                                                                        and vbak~auart eq 'ZOR'
                                                                                        and vbup~lfgsa ne 'C'
                                                                                        and vbup~absta ne 'C'.
    loop at gt_items.
    clear: gv_vbeln.
    clear: gs_ordhead, gs_ordheadx.
    refresh: gt_orditems, gt_orditemsx, gt_return.
    clear: gt_orditems, gt_orditemsx, gt_return.
    gv_vbeln = gt_items-vbeln.
    gs_ordheadx-updateflag  = 'U'.
    gt_orditems-itm_number  = gt_items-posnr.
    gt_orditems-reason_rej  = '93'.
    append gt_orditems.
    gt_orditemsx-itm_number = gt_items-posnr.
    gt_orditemsx-updateflag = 'U'.
    gt_orditemsx-reason_rej = 'X'.
    append gt_orditemsx.
    call function 'BAPI_SALESORDER_CHANGE'
       exporting
          salesdocument               = gv_vbeln
          order_header_in             = gs_ordhead
          order_header_inx            = gs_ordheadx
       tables
           return                      = gt_return
           order_item_in               = gt_orditems
           order_item_inx              = gt_orditemsx.
    read table gt_return with key type = 'E'.
    if sy-subrc ne 0.
       call function 'BAPI_TRANSACTION_COMMIT'
          exporting           wait = 'X'.
       message 'Sales order update was succesfull' type 'S'.
    endif.
    endloop.
    As result we get the following error :

    Hi Kurt,
    It looks like somebody has created custom logic (modification or enhancement) to display a screen. This results in an exception, as you currently executing the BAPI in a background process and not a dialog process.
    You can tell it is custom logic as the screen number begins with a "9", which are usually reserved for customer enhancements. 
    If you look at the source code extract in ST22 (Use the Tree Menu on the left hand side of the screen "Runtime Error"->"ABAP Developer View"->"Source Code Extract"), you can find the offending screen call. 
    You can stop the screen call logic by checking if the code is being run in background.  Check if the value of the system field SY-BATCH is set to "X", implying the code is being run in a background process.  If so then do not process the screen display logic. 
    Note you may need to add some logic to update the BAPI return fields with information pertinent to the screen that would have been displayed. 
    Cheers,
    Katan

Maybe you are looking for

  • Ora-06502 error while running a form

    Hi DECLARE pl_id PARAMLIST; begin      PL_ID:=GET_PARAMETER_LIST('TMP');      IF NOT ID_NULL(PL_ID) THEN           DESTROY_PARAMETER_LIST('TMP');      END IF;      PL_ID:=CREATE_PARAMETER_LIST('TMP');      ADD_PARAMETER(PL_ID,'PARAMFORM','TEXT_PARAME

  • Photo synch Problem

    Hello there! I' ve got a problem with photo synch via iTunes. Everytime I try to synch the photos( doesnt matter if try it with 1000 or just 10 photos), iTunes stopps at the first photo and tells me after a few minutes, that the synchronisation has b

  • When will updated firmware for the WRT600N be available.

    Since the IEEE has approved the 802.11N standard, we should expect updated firmware supporting the approved standard. Any guess when?

  • Why does the iPod Touch 5th gen 16 GB, not have a rear-facing camera?

    I am looking to replace my daughter's iPod Touch 4th Gen 16GB, but I can not find a model like hers that has a rear-facing camera. The new 5th gen 16GB, only has a front-facing camera, where the 32GB and the 64GB have front-facing and rear-facing cam

  • How to create Photo Album - Smugmug?

    Hi, I've been playing around with Photo Albums lately using PS CS, & DW's Fireworks version. They all work fine but I really like the way Smugmug is designed. The layout works well, and I'd like to create something similiar for my images. Any thought