Allow drag and drop additions/changes to POs.

Yeah. Good idea. But how about adding the option to transfer all non-received items to a new PO when committing. I do not understand how we are supposed to add items to our inventory count that are received when some items are backordered. I currently receive and commit, then create a new PO for the items that are on backorder... Not fun.

Digital Retail Solutions offers a product called PowerOps that will give you that option and a LOT more features besides -- I couldn't see using RMS without PowerOps, frankly. From the Power Ops help file regarding the Carry Forward feature (and there are like a skajillion other features it has):

Carry Forward allows you to close a partial PO and move the outstanding backordered items to a new PO. If your business routinely places pre-season or program orders on a single purchase order, this feature allows you to reconcile incoming invoices from suppliers that include items shipped to date.

You can only carry forward partial purchase orders and will receive this warning for other PO types.

The partial PO must also contain received items that have been committed (versus pending). Otherwise you will receive this warning. If the selected PO meets requirements, you will be presented with three options.

PO Number -- defaults to the original PO number appended with -01, or -02,

-03, etc. on subsequent runs if the same PO is carried forward again.

Include Inactive items -- uncheck this checkbox to prevent items that have been marked Inactive from appearing on the new PO.

Use current Description, SRN, and Cost -- when this checkbox is enabled any changes made to items on file will be updated to the new PO; if disabled the original PO content will be used.

Click Carry Forward to proceed. If successful, a confirmation box will appear.

I have considered many add-ins but never purchased one because I was afraid of what would happen during RMS upgrades. For example, I am on 1.3R, but what happens when I upgrade to 2.0, and then 3.0 ultimately. Is there more cost? Is it compatible? Will it become obsolete.

That is why I do not like add-ins, really. These suggestions are things that MS should really implement themselves - not rely on resellers. In my opinion, add-ins should be reserved for customer specific requirements - not features that everyone wants!

That's certainly one way to look at it.

I'm often willing to spend on a tool I needed to do my job more efficiently.

Jas> I have considered many add-ins but never purchased one because I was