Wednesday, December 30, 2009

Beware the .NET Framework 3.5 sp 1

DEX.DIC version 10.0.320.0 is not compatible with executable version 10.0.324.0

This error came up yesterday while trying to load the 2009 year end update. Going from build 1237 to build 1400 I did not expect any problems (my first error of the day).

This only happened on the new machines, not on the older ones. hmmm.

It turned out that the culprit was .NET Framework 3.5 sp 1. Every machine with 3.5 sp 1 on it threw an error. There was an old machine that I installed 3.51 on just to check, and sure enough, the same error. What to do . . .

I tried a variety of things, but here's what worked for me.

Choice 1 -- Download and install build 324 of Dexterity.

Choice 2 -- Simply copy the files from one of the functioning workstations to the one giving you a problem. You need to go as far as you can with the installation before doing this in order to load the Dex components.

Tomorrow we'll see if the Forms 1099 and W-2 print correctly after all of this effort.

Until next time!

Leslie Vail

Can't Import Excel Budget??

Here's the story. You export a 'blank' budget to Excel to make sure you have the format correct. You make all of your adjustments, save it and then try to import it back into GP.

Have you ever been thanked for all of your budgeting efforts with the message above?

You think -- but I exported the format from GP and then tried to import it back in, I didn't change it!

And I believe you :)

Check your column headings in Excel. If even one of your period descriptions is interpreted as a date by Excel, you will get the above message. Easy to fix, just turn it into a string and you're good to go. Don't forget to go into your Fiscal Periods Setup screen and modify your Period Name(s) so that it doesn't happen again.

Until next time!


Wasted, Unused or Voided Checks

This is a little tip for anyone who wants to keep track of all of their check numbers to account for 'voided' checks. By 'voided' I mean checks that were not actually used in a transaction, they were wasted. Like when someone prints a report on your check stock.

The method I use to record 'wasted checks' is very simple, here it is:

Go into Bank Transaction Entry, fill in everything except the amount. No
need to deal with the distribution accounts, leave everything zero. I usually
put 'wasted check', or something to that effect in the description field. It's nice to have something show up on reports. Post the check; boom, you're done.

I've recorded the wasted check and I don't have to do anything else.

I think this works very well and it keeps the auditors happy :)