Hi Susan,
In response to your questions. We are the designers/developers of your POA module. I appreciate your feedback.

1. Yes, you can edit an existing or create a new item. This sounds like a security issue setting. Go into the security profiles for the groups, use the expand all function to see all the settings for all menu tasks, and check to see if edit is on for the items. There is also a second security setting for the forms (the second tab beside menus). In POA, we allow you to refine the security of the function beyond simply maintain and inquiry. I suspect that the edit for Inventory items is not enabled for your security group, while add is enabled. Review the settings and enable the security settings required (by clicking).

2.The images function connecting to Inventory Items has been in POA since inception (5 years). We store 3 images for each item in Inventory, if you wish to use them. A single image was added in a recent update in Inventory, and I guess the common link between Inventory and Purchase Orders to enable images was overlooked in conversations between ourselves and Softrak. We will review with Softrak and see what can be done. There is a new release of POA version 8.0 that has been released in limited trials for about 6 months. We have been tuning and making modifications with this controlled release. We expect a full release shortly. The images linkage will not be addressed in the next release.

3.Posting a receipt always asks you to print a receipt now. We will note this and see if we can change this in a service pack to give the user the option as a runtime variable. I understand the annoyance.

4.In the company profile, on your runtime variables 1 menu, your reference cost on the detail screen is set for Standard Cost. You can cnage and choose between, recent, standard, cost1, or cost2. On the same runtime variables menu, you also get to choose how the various cost fields can be updated with the net cost, cost plus prorated misc charges, etc. The cursor should not stop on that field because you cannot edit the field on the screen. We will correct. This is an oversight on our development.

Regards,
Brian