Slow Triggers in Dataport

HalMdyHalMdy Member Posts: 429
edited 2004-05-14 in Navision Attain
Hello everybody !!!

First message, first problem, first help needed ... here we are :

I have one Export Dataport based on several tables. This dataport doesn't use a Request Form. Unfortunatelly, it takes a lot of time ( more than 1 minut) between OnInitDataport trigger and OnPreDataport trigger.

:?: Do you have any idea about what's the job done between these triggers and how can I make it more faster ?

:idea: To be complete, I work with a SQL base 3.10 version of Attain.

Thx for help and cheers !

Comments

  • RobertMoRobertMo Member Posts: 484
    any code there onInitDataPort ?
    Where are you exporting on local disk, network... etc.
               ®obi           
    ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
  • HalMdyHalMdy Member Posts: 429
    Here is part of the code, to be more complete ...

    OnInitDataport()
    Window.OPEN(Text7013464);
    Window.UPDATE(1,'1');

    ...
    //File to create is on Client hard disk
    CurrDataport.FILENAME:=CurrDataport.FILENAME+COPYSTR(str,1,pos)

    CurrFile.QUERYREPLACE:=FALSE;
    Window.UPDATE(1,'2');


    OnPreDataport()
    Window.UPDATE(1,'3');

    OnPostDataport()
    Window.CLOSE


    So time between display '2' and '3' takes more than 1 minut. No difference if I work on a network or if I first delete the file ... :?
  • RobertMoRobertMo Member Posts: 484
    Nothing suspicious.
    Do you really need this dialog to open in OnInit ?
    Maybe to open it on PreDataport ?
    Or you just use it to figure it out where the delay comes from ?
    What about debugging - same delay ?
    What exactly are you doing with filename ?
    Doy you have any other code OnInitReport (instead of ...) ?
               ®obi           
    ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
  • HalMdyHalMdy Member Posts: 429
    Finally, I understand !!

    There is no other custom code in the triggers. Simply, between OnInit and OnPreDataport, the system prepares the records to compute, with keys and filters defined in the properties of each table called.

    In my case, one of the filters is on a flowfied (lookup) wich takes a long time to be computed --> so dataport initialization is very slow.

    Hope this can help others in the future ...
Sign In or Register to comment.