Thanks to all of you who responded. One of my internal teammates, Phil Whirley, immediately deduced my error as he had direct access to the job. I'm sorry that I didn't attach it to begin with. The customer's source file has a comment that I populated into the header comment field without realizing that their comment is slightly different on each row. The different data on the header caused the job to advance EntryNo, which is set to Next.
By the way, before posting this request, I was on the phone with Sage support for an HOUR listening to the tech hem and haw and wonder and surmise and theorize and hypothesize to the point that I wanted to stab my eardrums.
------------------------------
Karen O'Lane
Accounting Systems, Inc. (ASI)
------------------------------
Original Message:
Sent: 07-21-2019 17:30
From: Beth Bowers
Subject: V/I Job to Import Journal Entries
Doesn't using Next and pointing to the date field work? (Seems to me like sometimes I get that to work and sometimes not)
------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625
------------------------------
Original Message:
Sent: 07-21-2019 17:20
From: Chris St. Amand
Subject: V/I Job to Import Journal Entries
You can use the posting date as the entry number If you only have one entry per date, using format MMDDYY or YYMMDD. One issue that comes up is when the import dates are not consistently 2 digit months and two digit days (i.e. 9 for September instead of 09). In that case, there are about 8 conditions that you would have to allow for. If you have a standard mm/dd/yy date format in your source data, you can bring in the date field as a Temp variable (Temp001 for example). The calculation would be:
Mid(Temp001$,1,2) + Mid(Temp001$,4,2) + Mid(Temp001$,7,2)
------------------------------
Chris St. Amand
Arizona Accounting & Information Systems