February 23rd, 2012· Made it so email addresses entered into the "CC" field are saved in a drop-down box, like the "To" field.
· Added "Quantity received" information to line item reports (if the Quantity received option is selected in configuration).
· Added several missing "hourglass" mouse pointers to common functions so that it's more clear what is going on when the program is being used in a potentially "slow" environment (the "cloud", etc.).
October 8th, 2010· Added an option to link text in a line item description to a URL, and improved the visibility of the existing option to link text to a local/network file. These features allow orders to have "clickable" links to other documents and/or websites imbedded in them.
March 30th, 2010· Fixed a couple bugs in the copy order function: First, before if an approved order was copied, the approval would carry over to the copy - that is corrected. Second, newly copied orders did not display correctly in the saved orders list until the list was refreshed (fixed).
January 6th, 2010· Updated the SMTP email send function to allow the use of 'StartTLS / SSL' encryption. Makes it so you can use many other email services (including Gmail) to send purchase orders.
June 12th, 2009· Fixed an omission wherein the vendor and destination reports did not create an .XLS file.
April 22nd, 2009· Made it so that you can specify a different SMTP port on the email send form.
March 16th, 2009· Added an option to import POs created on a remote installation and sent via email. Makes it so a buyer "on the road" can issue orders without being connected to the office.
· Added an option to insert "ASAP" in the on-site date field.
· Made it so orders can be printed with their internal notes included.
· Added an option which can greatly improved the program load speed and general operation speed when many hundreds of stock items are present.
June 18th, 2008· Fixed a bug where when e-mailing with the MAPI option and using ShareCon for addresses, the vendor's email address was not inserted
June 15th, 2008· Fixed a bug in the start-up password routine
April 25th, 2008· Fixed a bug that could (on some systems) cause a "Type Mismatch" error upon reloading an existing order.
April 10th, 2008· Fixed a problem where during the evaluation period the program could ask for a start-up password when none had been entered in.
March 26th, 2008· Fixed a bug that could cause a "Type Mismatch" error upon saving, when the approval system was in use.
· Made it so that empty vendor and ship-to address records are not shown when using the ShareCon option. (Use the full version of ShareCon to delete any accidentally empty records.)
· Made the routine which handles deleting items from the drop-down fields more robust.
March 15th, 2008· Made it so that when e-mailing an order, the subject line correctly reflects the custom wording you have set up, and the entire PO number (including prefix(es)) is included.
· Disabled the sent mail and mail error logging functions. These were undocumented, and may have been causing problems for some users.
February 2nd, 2008· Improved the speed of the .CSV / Tab stock item import somewhat, and added an indicator to tell you how many items are in your file.
· Fixed a bug where the Job Number entry field would accept more characters than are stored in the data file.
November 13th, 2007· Fixed a bug that would case a "type mismatch" error upon loading an existing PO. Only present in the Nov. 9 release. (Opps...)
August 16th, 2007· Documentation changes only (updated PAD file to current 3.01 specification).
July 25th, 2007· Added a currency conversion feature. Adds a single, final line on the printed order describing the conversion, and the converted price.
· Made it so that when you update prices in the assembly list editor, you can see what prices were updated, and also which items on the assembly list do not match anything in the stock items list.
· Made it so that you can delete assemblies from the list just before creating orders (click cancel, or make the quantity zero).
June 27th, 2007· Added an "Assemblies" unit - automatic order creation functions based on Assemblies lists. For example, suppose you manufacture a line of widgets. Each model of widget requires a certain number of parts, from various suppliers. With the PO Assemblies functions, you first create a list of parts for one of each model widget you build. Then when it's time to order parts for a production run, you simply select the correct parts lists, input a quantity of each model you need to buy for, and the program automatically creates purchase orders for each vendor for the total quantity of parts required.
Find us on Google+
