Sage 100

 View Only
  • 1.  error compiling VI job - error 13 VI_ImportJobCompile

    Posted 06-21-2019 16:11
    Hi
    We are writing some VI jobs ..  all going well (version 2017 su1) - but when we get to IM_transactionheader,
    to import opening inventory, the job bombs during the "compile"

    has anyone seen this before - nothing special about the import job....  and ones for CI_Item, IM_ItemVendor etc work fine.



    (error 13 in VI_ImportJobCompile.pvc Line 1571 while generating import program)

    Thanks in advance for any insight ....

    Will work around if necessary...

    Jeff F

    ------------------------------
    Jeff Fiddelman
    Exeplex, LLC
    ------------------------------


  • 2.  RE: error compiling VI job - error 13 VI_ImportJobCompile

    Posted 06-26-2019 13:16
    The manual says the following....

    File access mode invalid 

    Possible Reasons: 

    • Cannot send output to serial file unless first locked. 
    • Cannot receive input from an output-only device (e.g. a printer). 
    • Cannot send output to an input only device.
    • Cannot write given output to file without a KEY= option or not before extracting a record. 
    • Cannot write to a non-externally keyed file using a KEY= option. 
    • Cannot drop the only active window on a terminal. 
    • OS returned an access mode violation or a permission denied status on an OPEN INPUT or OPEN PURGE directive for a file. 
    • Attempt to apply/remove a password when the file is in read-only mode, not locked, or not empty. 

    So, with that said, can you open the table with DFDM, even if it is empty?  How complex is the VI script?  Can you recreate it under another name easily?

    ------------------------------
    Randy Marion
    ------------------------------



  • 3.  RE: error compiling VI job - error 13 VI_ImportJobCompile

    Posted 06-27-2019 11:32
    Jeff,
    ?????? Depending on the version, that might be a Column Names issue.
    Did you create VI job by copying and modifying another (earlier version) job?

    Code says:

    0027 READ (cFH,KEY=cJobName$,ERR=ERR_TRAP) ! VI_JobHeader info
    0029 LET retVal=_OBJ'GetTableInfo(TableName$,LnTable$,keyCols$,busObj$,UDT$,LLnTable$,OHTable$,OLnTable$,OIHTable$,OILnTable$,OCTable$,PYTable$)
    .....

    1571 SELECT tbl$,col$ FROM cAVMCH BEGIN $$ WHERE UCS(tbl$)=UCS(priTbl$) AND POS(UCS(K$[cix])=UCS(col$))
    (cAVMCH is a memory file with a list of available tables)

    Lee
    --

    Friendly Systems, Inc.

    Sage 100 (Mas90/200), Sage 300 (Accpac), SageCRM
    Visit us on the web at www.friendlysystems.com
    Office:?? 678.273.4010 ext 4
    Mobile: 404.202.9065
    Fax:?????????? ??678.273.4012
    See our blog at www.friendlysystems.com/blog



    ------Original Message------

    The manual says the following....

    File access mode invalid 

    Possible Reasons: 

    • Cannot send output to serial file unless first locked. 
    • Cannot receive input from an output-only device (e.g. a printer). 
    • Cannot send output to an input only device.
    • Cannot write given output to file without a KEY= option or not before extracting a record. 
    • Cannot write to a non-externally keyed file using a KEY= option. 
    • Cannot drop the only active window on a terminal. 
    • OS returned an access mode violation or a permission denied status on an OPEN INPUT or OPEN PURGE directive for a file. 
    • Attempt to apply/remove a password when the file is in read-only mode, not locked, or not empty. 

    So, with that said, can you open the table with DFDM, even if it is empty?  How complex is the VI script?  Can you recreate it under another name easily?

    ------------------------------
    Randy Marion
    ------------------------------


  • 4.  RE: error compiling VI job - error 13 VI_ImportJobCompile

    Posted 06-27-2019 13:12
    Thanks - I will dig a little deeper.....

    ------------------------------
    Jeff Fiddelman
    Exeplex, LLC
    ------------------------------