Illegal address for field ‘FICA/Med Add Tax Rate in script ‘941_Generate’

This error has been coming up lately in version GP2010. The solution has been to rename the Forms.dic. So, you need to export any modified forms to a package file. Rename your Forms dictionary and then import the package file, thereby creating a new Forms dictionary.
While I have only seen the forms dictionary needing to be renamed, start with renaming both the forms and reports dictionaries and then add them back one at a time. Or, just export all of your modifications, rename all of the forms and reports dictionaries and then import everything back in.

Update!  Robert said that he ran into similar issue when applying the GP2010 year end tax update. His error message was:

Unhandled script exception: Illegal address for field 'Medicare Wages and Tips Additional in script '941_Generate'. Script terminated.

He said this solution solved that problem too!
Microsoft has acknowledged this is an issue, but has not determined the exact reason.


Until next post!
Leslie

A Get/Change Operation on Table gpAppEnabled cannot find the table

 

This error came up after the ‘Technical Service Tools’, also known as the ‘Professional Services Tools Library’ was installed at a site upgrading from release 10 to release 2010 of Dynamics GP.

Once each of the 16 companies were opened by the ‘sa’ user, the problem went away. I suppose opening the company using the ‘sa’ user created the table that the system was looking for.

Until next post!

Leslie

David is on Page 4, vote for the best!

Hi guys,

Let’s put on a push this year to put the Top Most Influential Person in Microsoft Dynamics 2013 on the list.

You all know that I think this list is genius as a marketing tool (I wish I had thought of it), but if it’s going to be good marketing then it needs to be credible. Let’s put David Musgrave on the list and give it some credibility!

Vote for David here:  on Page 4.

Until next post!

Leslie

The MOST Awesome - Doug Pitcher

Doug,

Snarky doesn’t even begin to describe it! I love it! This ‘Other List’ thing has taken on a life of it’s own. I’m honored that a group of colleagues have decided that they can do better than anyone else on page 9! Boy, and they really have. I’ve gone from obscurity to the ‘man’ in first.

However, their efforts aside, I feel much more Awesome by having a high position on “Doug Pitcher’s OFFICIAL 100 most famous, awesome and totally influential Dynamics people for 2013” than anywhere on the ‘Other List’ (they snubbed me last year if my memory serves).

But Doug, there is no voting site for “Doug Pitcher’s OFFICIAL 100 most famous, awesome and totally influential Dynamics people for 2013”. I have mentioned to my team that cash would probably be as good as a vote, but I don’t think my ‘people’ have come to that yet. I’m thinking their loyalty stops at the whole wallet thing. OK, I know their loyalty stops at the whole wallet thing.

I would like to officially thank you for one hundred votes! How cool is that?, to be voted for by the owner of the REAL list of 100 most famous, awesome and totally influential Dynamics people for 2013. It just doesn’t get any better than this .

Page 9 is here: http://www.dynamicsworld.co.uk/the-top-100-most-influential-people-in-microsoft-dynamics-list-for-2013-page-9/

The Most Awesome list is here: Doug’s Most Awesome List.

The world watches and waits!

Until next post,

Leslie Vail

Updating the ‘Display in Lookups’ selections on the Account Maintenance window

 

You may have noticed that Integration Manager does not let you choose the individual selections for the ‘Display in Lookups’ field on the Account Maintenance window. It’s either all on, or all off. I used to use Table import to set the flags, but there is a much better way.

My thanks goes out to Tim Hickey of ConexusSG for showing me how to update this field using SQL. So much easier than table import.

Since the field GL00100.DSPLKUPS is a binary field, Tim converted the values for the multi-select list box to binary. He then used the corresponding value in a SQL UPDATE statement. Now, all of his clients (and you) can easily take advantage of this power feature in General Ledger.

For example, if you wanted to set the Payroll accounts to display only in the payroll module lookups (option 9), you would write something like this:

UPDATE GL00100
SET DSPLKUPS = 0X8
WHERE ACCATNUM in (39,36)

Take another look at your chart of accounts, and use this feature to help speed up account selection. The table below has every option you can choose for the ‘Display in Lookups’ field, along with the correct SQL value.

Enjoy!

Option	Image	SQL	Binary
1		0X0	0000
2		0X1	1000
3		0X2	0100
4		0X3	1100
5		0X4	0010
6		0X5	1010
7		0X6	0110
8		0X7	1110
9		0X8	0001
10		0X9	1001
11		0XA	0101
12		0XB	1101
13		0XC	0011
14		0XD	1011
15		0XE	0111
16		0XF	1111