While trying to login to Sage 300 ERP application or accessing any Sage 300 Company, users may encounter an error such as “Cannot access database (error=49153). See Help for more information” New Stuff: – Project Job Costing – Project Style option in Contract Maintenance In this blog we are going to discuss about the solution… Read More »
While trying to login to your Sage 300 Company on Sage 300 workstations, sometimes users face an error “Database Error 49153”. New Stuff:: Enhance Security in General Ledger in Sage 300 v2018 In this blog we are going to discuss the solution to resolve this error in detail. Solution: Go to registry by typing regedit in… Read More »
How you organize your chart of accounts depends on how you intend to use a particular feature of the General Ledger system. You must decide: Which accounts you need. Which account segments each account requires. How you will assign account numbers. Begin by listing the accounts you need, and then decide on an account numbering… Read More »
In our previous blogs which are related to integration, you can notice that all are related to import – export process. Previously for entering a data in the program, we needed to co-ordinate between the data files like excel, xml or text and then input the same in the program and create an entry into… Read More »
Sage 300 ERP (formerly Sage Accpac ERP) introduced a new feature, wherein user can assign different color to every company in Sage 300 and can easily identify multi session opened for different companies in single screen. Note: Before starting to use this functionality, it is recommended to install PU1. In this blog, we would discuss… Read More »
You come across Database profiles table error while opening the database Setup utility on a Sage (Accpac) 300 ERP workstation. It may persist even after you assign all Read\Write rights to the system and windows user on Sage Accpac folder in installation directory. This type of error occurs due to invalid path of Programs and… Read More »
In Sage Accpac ERP, if you design a report using one Database say e.g. “SAMINC” and when you deploy it at clients end where database name is different say “SAMLTD”, then sometimes while executing the custom report through the custom report UI you get a error message “Logon failed” as shown on below screen. This… Read More »