I've seen some significant problems with Nod32 AV as well so I avoid it.
(There's a TechTip).
Regards
JayJay
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
That was it. An existing program was not in the list. When I loaded from TEST
to PILOT, it was skipped and was running the earlier code.
I have to assume it was my mistake, but BOY did that cause some confusion!
PRC is a good tool, but you have to use it correctly (which apparently, I did
not
You should use SRC (or F8 in PRC) to check if all processes are actually
part of your project.
When working on multiple projects it can easily happen that part of one
project ends up in a different one.
So while everything works fine in development or test when you load it
parts of the project m
You got that right!
Actually, it looks like one of the programs was missed and it was running the
prior version. No clue how or why, but I think I am on the right track.
Sorry for the panic message.
Merry Xmas to all!
John
John Israel
Senior ERP Developer
Dayton Superior Corporation
11
The problem's obvious: you're working during your vacation!!
Sorry, I don't know how PRC pushes the updates - but I'd start with /XP or
/MP and go through the processes to make sure everything's calling what I
expect (guessing that PRC didn't overwrite a current process that is setting
things so i
I am dying here!
We use PRC to push our SB stuff from TEST to PILOT and then from PILOT to LIVE.
I wrote a new process in TEST that works perfectly. It looks for some txt
files to import. If found, and you hit F2, it does some validation before
importing. No problem.
I used PRC to move this
No idea if this is still relevant to you, but I found this thread when trying
to
solve the same problem, as we are looking to migrate to Win 2008 r2.
The root of the problem is that splwow64.exe (32 bit print processor for
Windows) is loaded on demand. By default it stays resident in memory for
