Sage 100

Need some help. MAS 90 3.30. that's right, 3.30. err 46, imzuab, line 6310 when attempting to update phy count variance register. error is on imm file (i/m component usage history file), channel 32767, key = ""100 WIP SD 0111?;05135072

at this point we now have the ""update interrupted, do you want to continue?"" message. client does use b/m module

and the client has tried to restart the update several times.

Does it always error out there? And what if you look inside IMM for that key ? Can you see damage? Get the key out of there?

The component usage file is used to record the activities of components on sales kits or instances where inventory is issued out by whatever module. I would look at the IMM file and for that part number. Something wrong there. You might want to try to rebuild the key of that file if possible

Error 46 is invalid string size. To me problem is bad record in IME. 6310 LET IMM$(1,22)=K1$(4,15)+K1$(1,3)+INV_YEAR$, E1=IMM_CH,E2$=IMM$(1,22) READ(E1,KEY=E2$, DOM=*NEXT) IOL(IMM

Sometimes troubleshooting would be a lot easier if we all had access to the source code.

It can also be that the E1 file channel is no longer pointing to the IMM file. Type this at the debug prompt: ? PTH(E1) It will return the file name from E1 channel. See if this points to a file other than IMM (who's key size is not 22 ergo Error 46)

Thanks, all! Glad to know I was on the right track with this one. Attempted the Rebuilds but no help. I had figured I'd find a bad record somewhere (IMM? IME?) but I wasn't seeing anything. I ended up yanking the record referenced in the error, from the IME phy ct entry file and that seemed to do the trick. But then it error'd on a different record. So I deleted that one as well from IME - in hopes that this wasn't gonna go on and on for tons of records. Was then able to successfully update the phy ct var reg with those 2 records removed from the IME. And actually those 2 weren't really technically needed in phy ct entry because the phy ct matched the on-hand qty - therefore no resulting variance. Still don't know exactly what the cause of the error was but found out that the last time they used phy ct entry was about 5 yrs ago. And then of course because the client had attempted to restart the Update multiple times, they now had various duplicate phy ct var transactions. So in the end they had to re-enter their phy ct entry, and then adjust the gl accordingly. @AlnoorCassim, I didn't have a chance to try your suggestion because we had resolved the issue already.

Doesn't socialcast/90minds kick ass or what?