Sorry for stabbing in the dark here....posting in a few places as I don't know where (if anywhere) this belongs.
I don't know what this code is written in; not sure where to post this. I'm hoping the programmers out there will know intuitively.
I have an import that doesn't work properly. It will not pick up quantity 11 -- 9 works; 10 works; 12 works and so on. Just 11.
The software is some proprietary thing with the DB software we bought and I don't want to pay for them to fix the import -- it may well be a change in our data file that feeds the import so I thought I'd see if I could find the problem. Doing this also gives me the ability to make minor changes that I know I can do now without paying them.
I found many of the pieces of this import and found this file definition file which identifies the database fieldname, size to read, and misc conversions. The STAT later refers to a table that converts the input field into a new value (input as status A - converted to status O). The SKIP -1 clearly has it back up to re-read the same last digit of the qty and match it to the digits 1, 2, thru 9. Then after, backs up again to get the full quantity.
The 8 is said to be ASC LEN, the 0 ASC PRE, the first "" is teh DEFAULT, the 2nd "" is the TRANSLATE table, the third "" is the PIC (and happens to be never used).
*FIELD DATE 8 0 "" "" ""
*FIELD TIME 5 0 "" "" ""
*FIELD ORDR 9 0 "" "" ""
*FIELD STAT 1 0 "" "STAT" ""
*FIELD SKIP 3 0 "" "" ""
*FIELD MATCHOR 1 0 "1" "" ""
*FIELD SKIP -1 0 "" "" ""
*FIELD MATCHOR 1 0 "2" "" ""
*FIELD SKIP -1 0 "" "" ""
//continues the same 2 lines for 3,4,5,6,7,8 and finishes with:
*FIELD MATCHOR 1 0 "9" "" ""
*FIELD SKIP -4 0 "" "" ""
*FIELD QUANTTY 4 0 "" "" ""
Any idea why it is checking this last digit for 1 thru 9? Any idea why this would not work for 11 but does work for 10, 12, etc?
From this I'd say it must be in the hard code I can't seem to get to.
Thanks so much for even reading this and possibly helping out!
I don't know what this code is written in; not sure where to post this. I'm hoping the programmers out there will know intuitively.
I have an import that doesn't work properly. It will not pick up quantity 11 -- 9 works; 10 works; 12 works and so on. Just 11.
The software is some proprietary thing with the DB software we bought and I don't want to pay for them to fix the import -- it may well be a change in our data file that feeds the import so I thought I'd see if I could find the problem. Doing this also gives me the ability to make minor changes that I know I can do now without paying them.
I found many of the pieces of this import and found this file definition file which identifies the database fieldname, size to read, and misc conversions. The STAT later refers to a table that converts the input field into a new value (input as status A - converted to status O). The SKIP -1 clearly has it back up to re-read the same last digit of the qty and match it to the digits 1, 2, thru 9. Then after, backs up again to get the full quantity.
The 8 is said to be ASC LEN, the 0 ASC PRE, the first "" is teh DEFAULT, the 2nd "" is the TRANSLATE table, the third "" is the PIC (and happens to be never used).
*FIELD DATE 8 0 "" "" ""
*FIELD TIME 5 0 "" "" ""
*FIELD ORDR 9 0 "" "" ""
*FIELD STAT 1 0 "" "STAT" ""
*FIELD SKIP 3 0 "" "" ""
*FIELD MATCHOR 1 0 "1" "" ""
*FIELD SKIP -1 0 "" "" ""
*FIELD MATCHOR 1 0 "2" "" ""
*FIELD SKIP -1 0 "" "" ""
//continues the same 2 lines for 3,4,5,6,7,8 and finishes with:
*FIELD MATCHOR 1 0 "9" "" ""
*FIELD SKIP -4 0 "" "" ""
*FIELD QUANTTY 4 0 "" "" ""
Any idea why it is checking this last digit for 1 thru 9? Any idea why this would not work for 11 but does work for 10, 12, etc?
From this I'd say it must be in the hard code I can't seem to get to.
Thanks so much for even reading this and possibly helping out!
