OK, this post might seem really anticlimatic, but I had to throw in a post to finish the story. 

Read the rest of this entry »

 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.”

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.

This year’s WWPC is rapidly approaching. Despite the difficult economic climate, thousands of Microsoft partners will descend upon the Big Easy this month. Read the rest of this entry »

To set the trace flag

Step 1.     Open SQL Server Configuration Manger.

Step 2.     In the left pane, click SQL Server 2005 Services.

Step 3.     In the right pane, right-click SQL Server (MSSQLSERVER), and on the shortcut menu, click Properties.

Step 4.     In the Properties window, click the Advanced tab.

Step 5.     Click the Startup Parameters property, and open the drop-down list.

Step 6.     Type ;-T4616 at the end of the line in the drop-down list and click OK.

Step 7.     In the right pane, right-click SQL Server (MSSQLSERVER), and on the shortcut menu, click Restart..

An interesting article from Chris Kanaracus of PCWorld: Read the rest of this entry »