Recent content by RWCinci

Thanks! It worked just fine. I kinda thought that was the solution, but it has been a long time since we had to do it and I wanted to verify. Again, thanks! RHW

Ooops, forgot to mention: This batch is in GL and was brought over from AP. Regards, RHW

Hi, I have an AP Batch that refuses to post. When I highlight it and click Post, it says "Batch has not been made Ready to Post, do you want to post this batch?" When I click OK, it comes back and says "There are no batches Ready to Post" but the Ready to Post status has been changed to...

Do you know the earliest version of Accpac that is compatible? Also, is it just a matter of the pervasive sql or does it go deeper than that? Thanks, RWCinci

Has anyone had any experience with Accpac 4.2 running on Vista? I tried setting it up with Pervasive 2000i on a new Vista Business machine and so far it is a bust when trying to use a workstation install. I'm not sure if 4.2 is the issue or Pervasive is the issue. When it tries to start it...

Hi, I appreciate your response! The error posting journal report indicates a date error, i.e. a date was outside the financial calendar. Unfortunately, we can't get in to correct it. I ran the data integrity check for a second time with the same result - no change in the batch status and no...

A batch of several items was created in the AP Invoice Batch List module. On posting, one of the items appeared to "stick." We attempted to fix with Restart Maintenance as suggested by the dialogue box which appeared. All the items except 1 posted and the rogue item ended up in an "Error...

Final update. This problem is resolved by applying patch 10 or Viruscan Enterprise 8.0i. Thanks very much for helping me out. Regards, Dick Walter

It is definetly related to Viruscan Enterprise version 8.0i. When we remove it the behavior disappears and when we operate the workstation with Norton AV, it operates normally. Thanks again for your help

Thanks very much for this reply. Now that you mention it, the latest workstation came with Symantec installed on it. After Symantec expired, we installed Mcafee as we have a corporate license for it. It began misbehaving shortly thereafter. I'll take thing sequentially and report back...

Over the past several months our XP workstations have developed an issue. I'm not sure if it is due to XP updates, virus updates (McAfee) or other issues, but now all of the machines behave the same way. Each time a user opens a new module a dialogue box pops up with "A4WRLZS.EXE has...