AirWolf
Honorary Master
Sage people very reluctant to offer public advice I see.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Sage people very reluctant to offer public advice I see.
That's because Sage charges for every support callthey want you to phone them.
BTW where did you learn to write Crystal Reports (if you don't mind me asking)?
Sage VIP 4.5a Classic
Problem exporting garnishee orders. Only exports the first garnishee on employees with multiple garnishees.
Need to check how far back the problem started when back at the office tomorrow.
**Suspect it started after I installed 4.5a in November.**
Called the call centre earlier - they said I should extract the 4.5a patch to the VIP classic folder, which I did - problem still exists.
We are using FNB though and not Standard Bank which the patch notes referred to.
Any ideas?
Sage VIP 4.5a Classic
Problem exporting garnishee orders. Only exports the first garnishee on employees with multiple garnishees.
Need to check how far back the problem started when back at the office tomorrow.
**Suspect it started after I installed 4.5a in November.**
Called the call centre earlier - they said I should extract the 4.5a patch to the VIP classic folder, which I did - problem still exists.
We are using FNB though and not Standard Bank which the patch notes referred to.
Any ideas?
Yep, problem started after I installed update 4.5a in mid-November 2015.
Of the garnishee list, only 3 employees have 2 garnishees. All 3 are missing the second garnishees (all different garnishees) from November to February. Strangely one of the 3 employees did have both his garnishees go through in December only, but the other months it does not export.
I have something you could possibly look at and test, Its an issue which has been bugging be since many versions ago of Accpac.
If I remember correctly this issue comes from 5.3 even up until Sage ERP 300 (Version 6.1A)
When posting and shipping items from an order in order entry, there is a popup screen that asks if you want to print the shipment, If user leaves the box open it creates a lock on the database (Not a dead lock) and (Using MS SQL Server 2008)
And I have a very good idea why this happens.
When you select no you do not want to print the lock will go away and the screen terminates normally, when you select Yes you want to print it, It will flag the shipment as printed in table OESHIH.PRINTED or ISPRINTED or what ever the field's names is I don't have the object model in front of me right now.
Initially you we were generating Invoices directly from Order entry but our operations changed slightly and we are now generating documents Orders-->Shipment--Invoices but even if the setting is set to generate invoices directly from Orders in the OE setup screen it also locks the database as explained it think it then updates both OESHIH.PRINTED and OEINVH.PRINTED
Not sure what the solution will be but maybe it will help by letting the screen open with query (OESHIH.PRINTED with no lock)
I cant see how the printed flag is important enough to open the table and with a hard lock.
I would be very surprised if other people don't experience the same issue on MS SQL Server , In between upgrades we have moved from physical to virtual using brand new OS installations and the same problem has always been there.
Funny enough its only one user out of 50 that leaves the screen open and then go on lunch.
Where can I find a list of partners for biometric clocking systems that integrates into VIP Payroll?


Is it possible to connect to VIP Premier from an application using a connection string?
I've seen hints that it might be an Access database, but I can't confirm. Even the consultant at Special Solutions wasn't sure, all he knew was that it was written in Cobol.
The only ODBC functionality I use is the StatsSA excel report, which is painfully slow.
Sage Evolution:
Have one stock item that shows different quantities at the same date on two different reports:
- Valuation report on a particular date;
- Movement report over say a month.
How do you fix this as in theory any posted entry should affect both the same.
The error actually goes all the way back to October 2013.