Form closes when posting the Purchase Invoice

Waldo

I have a strange situation at my customer's navision implementation.

A few days ago, I did an exe-upgrade (only exe, object-upgrade will be done in May) from Navision 3.01 to 3.60. Now, since a few days (so, I suppose it has something to do with the exe-upgrade) when someone posts a purchase-invoice, the form just closes when the invoice is posted. Everything is done well (posting routine), but the form closes. And the strangest thing about that, is that it doesn't happen all the time (yes, most of the times, but not all the time).

Alse, since then, once in a while they get "purchase invoice does not exist" when posting purchase invoices. Again, the posting routine has done its job, but the error-message is strange ...

Can somebody help me with this?

luke

Hi,

there is a new client update available for NA 3.60, this should help
your problem, because it helped mine !!

Waldo

Thank you very much for this wonderful news.

I only have a small problem finding the new client. I have been searching the navision-ftp, the navision-partnerguide, but nothing found (yet). May be you can give me the exact location of where I could find this update?

Thanks in advance!

Waldo

I have been digging into this problem, and I found a workaround, which can be useful for everyone, since the problem exists in the standard 3.60. First I will give you an exact description how you can reproduce the problem:

1) Create an Invoice (I only tested it with purchase invoices) 2) Post + Print (Then you go back to the Main Menu) 4) Create a new invoice 5) Post + Print (Then you get an error with a description of the previous correctly posted invoice).

Very important to reproduce, is that your cursor stays on the Subform.
Conclusion: completely bizar!

Now, here's a workaround: change the relevant object(s), force the cursor to be on the header all time you print something:
Put this code in the OnPush for Post+Print menu item:

OnPush
CurrForm."Sell-to Customer No.".ACTIVATE;

What I found on this issue, is, that it is a bug that occurs since the 3.60 and will be fixed in Rhodes. I also found that this problem occurs on the sales-side as well as on the purchase-side. It also seems that this bug occurs when printing a test report, but, again, the same solution can be implemented there too.

I have been searching for a new fin.exe of version 3.60, but I just can't find one. Off course, that could solve this problem too, but this workaround can be useful.

Enjoy!