15 to 30 second delay when selecting PO fields in Great Plains 7.0

[foxforce5]

We have several users that are experiencing a strange delay when thay click into the PO Number field on the .Purchase Order Entry Screen. After 10, 15, or somtimes 30 seconds Great Plains minimizes to the taskbar. After maximizing the screen the fields are usable and there are no more problems on that PO. Similar problems appear when you click the 'link' button to view the associated Purchase Order in the Sales Order Inquiry and Sales Trx Entry screens, as well as the Purchase Order Inquiry screens.

We are running the clients on Pentium 4, 1 GB RAM desktops, and we have reinstalled that application as well as reapplying the permission in Advanced Security.

Any help would be greatly appreciated.

foxforce5

 

[BobSchleicher]

Since you are showing .Purchase Order Entry that shows that the screen has been modified.

First I would try to open the unmodified version and if it opens without any delay then I would say that the modifications may need to be looked at.

BobSchleicher

 

[jazgeek]

please check PO setup and find out what the next PO# is set at. If it is set to a # that is lower than your most current PO#, GP must scroll through all PO #'s in series to find the next useable PO#.

I'd also check what BOB's saying too above.

-----------
and they wonder why they call it Great Pains!

jaz

 

[foxforce5]

Bob and jaz thanks so much for your responses. Unfortunatley, we have never used anything but the .Purchase Order Entry screen and we are unable to change back to the orignal.
Updating the PO Setup to reflect a number closer to the POs that we are using had no cange on the problem either.

foxforce5

 

[BobSchleicher]

To use the non modified screen just go to the security of a user and remove the modified screen under modified windows under purchasing.

BobSchleicher

 

[foxforce5]

The only items listed under Advanced Security | Purchasing are Stanard and Drop-Ship.

 

[jazgeek]

expand in advance security

by dictionary
great plains
forms
purchasing
purchase order entry

should be two there one for great plains, one for your modified


-----------
and they wonder why they call it Great Pains!

jaz

 

[foxforce5]

Thanks for the step-by-step. Unfortunaley, it had no effect on the problem.

Do you think that we should delete and re-create the user accounts in the system?

 

[jazgeek]

before you do that, please change your PO #ing format to something completely different and see if that makes any difference. I still think it has to do with the PO #ing sequence.




-----------
and they wonder why they call it Great Pains!

jaz

 

[foxforce5]

Sorry Jaz. No changes.

 

[Luvsql]

Some other things to try:

Go to setup > System > Security (don't use adv security). Change the company, user ID, Great PLains and go to modified reports. IS there anything listed? Try for each additional product, with the Alt modified Dyn window.

Do you have a Dynamics.vba file located on that machine? Edit it and see if there's anything in it.

Go to file > maintenance > Sql. Change database to yours, product is Great Plains, (make sure you are logged in as sa). Located the Purchase Order WOrk file. Mark both the drop and recreate Auto Procs. Once done, run the grant70.sql against that database.

 

[Luvsql]

To rule out an issue with modifications, create a brand new user and do not assign it to a class ID. Do they have the issue? If so, then it's not the window.

 

[Dukester0122]

If luv suggestions doesn't help, try these options:
1. Reindex the POP tables
2. Recreate POP stored procedures
3. Remove completed POs
4. If you check your PJOURNAL table do you have a lot of records? If so, delete this table. If you don't see a significant improvement in performance then you will need to record a trace of the PO entry and analyze it for errors.