 |
|||||||||||
|
Approximately 68% of online users use some form of cloud computing, defined as any web based activities that involves storing data and/or accessing online applications. Read the rest of this entry »
The world’s top ERP vendors will team up for the ERP Vendor Shootout. Read the rest of this entry »
Microsoft announces its new CRM Accelerator, which pulls data from social networking sites and integrates it into its CRM system. Read the rest of this entry »
There’s a new .fob viewer download that allows you to view the listed objects in a particular .fob file. You can also load 2 files at once and compare the objects between files. You can save, print, and export the list to Excel. Handles object types: Table, Form, Report, Dataport, Codeunit, XMLport, MenuSuite, Page.
Download it here: http://www.mibuso.com/dlinfo.asp?FileID=1112
I sometimes sound like a broken record when I talk about speed issues at a customers site. “It is usually not the hardware, but rather the code running on it.”
On July 6, Sage’s largest partner in 2007 and 2008, MIS Group, suddenly shut down. Read the rest of this entry »
I guess it is quite apparent that I am having my days with the MAS system. So far, I have not seen anything that NAV can not do out of the box, until I got to the return orders. ( Mind you, I am not, and do not claim to be an expert on MAS )
In the return orders, apparently you are able to select multiple documents in MAS to apply to when you post the credit to the customer. This is not possible in NAV standard. We have however bridged this gap with a few lines of code, leveraging the power of NAV.
When you create a multi line entry in e.g. the cash receipt journal in NAV 5.1 and happen to have the same customer in two lines (customer might be paying with two checks). If you go to apply entries on the second line after applying on the first one, the system filters on your applies ID and the document number, not the line number. Therefore the totals include the previous application, which throws the system off a little. You can still post without a problem.
An easy fix to this would be to account for the line number as well as the document no when going to the applies to screen.
The error message:
2705,”42S21″,[Microsoft][ODBC SQL Server Driever][SQL Server]Column names in each table must be unig. Column name ’securityoption’ in table ‘dbo.$ndo$dbproperty’ is specified more than once.
SQL:
ALTER TABLE [dbo].[$ndo$dbproperty] ADD securityoption INTEGER NOT NULL DEFAULT 0
Unfortunately, this error occurs quite often when “converting” a database. The problem is, that the field “securityoption” is added to the table “$ndo$dbproperty” in the beginning of a conversion. Once the upgrade fails, the transactions are not completely rolled back, the field “securityoption” still remains. Now if you try to convert again, this error is raised, because C/SIDE tries to add this column again.
To solve this, you have to delete the field “securityoption” manually from the table “$ndo$dbproperty” via Management Studio and run the conversion again.
I tried installing nav 3.7 on windows server 2008 and it does not work.
