Great Plains ver7.5 Bug Report II

Let me rephrase the title because GP don't use bug, instead I'll use Great Plains ver7.5 Product Report II.

In Smartlist, sometimes a user can accidentally open an object by mistake. In this case instead of using Receivables Transactions, he/she opens Receiving Transactions. If this happen, you'll get this message:

FP: Null Field Address Form: - XX Wind:XXX Fld:XXXX

When you close the message, the Unhandled script exception error opens. Now you can't get out of the error mesaage and you're stuck. The next thing the user needs to do is contact the Great Plains administrator to clear your userid in the database or use User Activity to delete your session.

I've reported this to GP and the PR code is 42126 which they said doesn't appear that it's slated to be addressed in the coming releases.

If you experience the same error on other objects, please go to CustomerSource and report the incident. The more PR code created of the same nature, will move the PR priority even though this isn't a critical error to resolve in the first place.

Tek-tips Question I

I'm going to create a series for Tek-tips questions from Great Plains users. This maybe a simple question or complex question but would be handy for new and old users of the system.

The first would look at Drop-ship sales orders. Here's the user question:

"We are having a problem with the invoicing distributions when we post a drop ship order. We have a mysterious entry showing up at the end that is not visible in the original distribution screen. It is type for inv and cogs. Does anyone one know where it is coming from?"

ANSWER:
Inventory and Cost of Goods Sold are created during invoice posting and should be coming from the sale line item distribution accounts. This is by design because the cost of the items are not known until the invoice is posted.

If the sales line item distribution is blank you can manually enter accounts, some companies do this whenever a non-inventoried item was entered.

If this is an inventoried item, the accounts should be coming from the item card. If the Drop Ship items account is blank on the item card the system would look at the posting setup for inventory (Setup>Posting>Posting Setup>Display:Inventory) then Drop Ship Items.

Microsoft Dynamics Brand

I've been reading a lot about the new branding that Microsoft did to its MBS products and I thought why not give my own opinions about it.

Back to old times I would say.

Yesterday, it was Great Plains Dynamics Ctree or Btrieve and Great Plains eEnterprise.

Today, we have Microsoft Business Solutions–Axapta, Microsoft Business Solutions–Great Plains, Microsoft Business Solutions–Navision and Microsoft Business Solutions–Solomon and Microsoft CRM.

Tomorrow, it's going to be Microsoft Dynamics CRM, Microsoft Dynamics GP, Microsoft Dynamics AX, Microsoft Dynamics NAV, Microsoft Dynamics SL.

Do you see any resemblance?

Error: Failed to Export the Report

When you try to print a document in Great Plains and you're using Forms Printer, you get the following error: Failed to Export the Report.

Solution:

Crystal Reports 8.5: Copy all Crystal Dlls from C:\WINDOWS\Crystal folder to the C:\WINDOWS\system32

Crystal Reports 9.0: Copy the Files in C:\program files\Common Files\Crystal Decisions\2.0\Bin TO C:\WINDOWS\system32

Crystal Reports 10: The path is C:\program files\Common Files\Crystal Decisions\2.5\Bin

The recommended way is to copy the files but don't overwrite any existing files in Windows\system32, but just add the Crystal files.

Adding more audience to this blog

To cater to a broader audience, I've decided to add Crystal Reports. I've been helping a lot of users in MBS Great Plains community site and Tek-tips in how to create, look for sql tables or even linking tables.

FRx 6.5 error in Windows Server 2003

We're upgrading all our servers to Windows Server 2003 and the last servers for upgrade were the SQL Server and FRx. When we try to start FRx 6.5, we get Error 339 on CSTEXT32.OCX.

I found an article in CustomerSource on this error:

CAUSE

FRx 6.5 has been installed on a Windows 2003 Server. Service Pack build 6.5.152 (Service Pack 4) has been applied, instead of the Windows 2003 Hot Fix. The Windows 2003 Hot Fix is required in order to successfully start FRx 6.5 on a Windows 2003 server.

RESOLUTION

Download and apply the Windows 2003 Hot Fix on the Windows 2003 server. The Windows 2003 Hot Fix is located on PartnerSource, CustomerSource, and the Great Plains FTP site:

PartnerSource -
https://mbs.microsoft.com/partnersource/products/
greatplains/downloads/hotfixes/frx65w2003hotfix.htm

CustomerSource -
https://mbs.microsoft.com/customersource/support/
downloads/hotfixes/frx65w2003hotfix.htm

Database and application versions do not match error in Enterprise Reporting database

When you try to log on to a Microsoft Business Solutions - Enterprise Reporting database, you receive the following error message:

Database and application versions do not match. Please contact your sales representative concerning an upgrade.

This problem occurs if the name of the Microsoft SQL Server database on the server includes a space. Before you follow the instructions in this article, make sure that you have a complete backup copy of the database that you can restore if a problem occurs.
To resolve this problem, rename the database by using a name that does not contain a space.
To rename the database, follow these steps:
1. Start SQL Server Enterprise Manager.
2. Locate the database whose name contains a space. Make sure that you know where the .mdb file for this database is located on the server.
3. Right-click the database, click All Tasks, and then click Detach Database.
4. Right-click Databases, click All Tasks, and then click Attach Database.
5. In the Attach Database dialog box, locate the .mdb file for this database.
6. In the Attach as field, rename the database. Use a name that does not contain any spaces.
7. Update your Open Database Connectivity (ODBC) connection with this new database name.