Core Financial Modules

[dlevasseur]

When clicking the lookup button in AR->InvoiceHistoryInquiry->Memo I receive an error box:

Title:  Lookup AR_InvoiceHistMemo, Error #41: Invalid integer encountered (range error or non-integ...(It cuts off right there)

Body: Error in lookup AR_InvoiceHist Memo

There is nothing else except an "OK" button (no Info button like the standard MAS errors).  This happens whether an invoice has memos or not.  Also, with invoices that I know have memos, I can use the directional arrows (next, last, etc) properly.  This error only occurs when clicking the lookup glass.

I have tried rebuilding sort and key files for AR_InvoiceHistoryMemo with no luck.

Error is found in both our production MAS90 4.4.0.1 environment and also our test 4.4.0.2 box.

Anyone else have this error, or an idea on how to fix it?

EDIT:  For giggles I blew away everything in the AR_InvoiceHistoryMemo.m4t file on my test box, still no luck.

[VKZIMM]

I do not think it is your file, it is a lookup so instead of clicking on the magnifying glass, click on Custom and see what is out there and delete any custom lookups or maybe you had a UDF display that does not exist.

I had a client with a similar error.

Good Luck.

[dlevasseur]

OK.  I clicked Custom and there are no custom views out there.  So just for testing I created a new default view called "View1" and left only the required field "MemoCode".  Now I receive this error:

Custom lookup is corrupt.  Use Custom to delete and recreate.

(Lookup AR_InvoiceHistMemo, Error #41: Invalid integer encountered (range error or non-integer), at line 1000)

Click OK to display Standard lookup.

After clicking OK I get the same error in the original post.

hrm...

[TomTarget]

Does this happen for all users?

[dlevasseur]

Sorry I forgot to mention.  Yes, as far as I can tell it happens to all users including myself who has permissions for everything.

EDIT:  And different workstations.

[BShockley]

Have you tried changing the screen resolution on the workstation?  I've seen some strange things with screen resolutions being too high.

Do your workstations have plenty of memory?

If you run MAS 90 from the MAS90/Home/PVXWIN32.EXE file, is the problem duplicated?

Type run "startup.m4p" at the prompt to start MAS 90.

[dlevasseur]

Just tried all of that with no luck.  Ran through several screen resolutions.

I don't have any workstations less than 2gb of memory.

EDIT:  Also, on my test box I have my 4.3.x install from before the 4.4 migration.  So I opened that up and the problem existed there as well.  So the problem must have existed for some time and just never came up. 

[TomTarget]

If you look in the system activity log, can you see the error listed with a little more info such as the program name and line number?

If it is, put the error #  program name and line number into the knowledgebase and see if that scores a hit.

[dlevasseur]

Tom,

No errors are reported in the activity log.  The log looks surprisingly clean actually...

-Dan