Answer: You may be printing a purchase order that is coming up blank.  This can happen as the result of several things.  Below are the possible circumstances and resolutions to the problem.

1. At one time a copy of the original data was distributed with a defective purchase order document report.  This has been corrected for over a year but occasionally a user reports the problem.  Because we do not want to overwrite any user’s customized reports, we are unable to redistribute the report automatically.  It is possible you have the defective version of the report.  You should click on the link below to download the original report template.

2. The report is linked to parts or some other table where records do not match or no records have been entered.  Check the purchase order data to insure that valid vendor and parts are selected.  If the problem persist even though you know all data is correct, consider item 3 below.

3. The report may have been alter in the Data tab in such a way that the report no longer returns any valid data.  Users are free to alter and customize all reports.  However, altering the query in the Data tab can render the report where it no longer returns any valid records.  This is usually the result of incorrect table joins.  You can check and attempt to correct the query or you can download and import the original report template from our website from the link below.

Click Here to download any original report templates from Express Technology Inc.

Answer: By default ExpressMaintenance allows you to have duplicate PO numbers in the purchase orders.  However, you can limit this by going to Administration / Defaults / PO Defaults.  Select the option Warn on duplicate POs and change the value to Yes or No as desired.

In addition, you may need to adjust the database table constraints to allow for duplicates.  To do this, you can use the option under Utilities / Run SQL Statement or you can use ExpressSQL or some other SQL program to execute the following commands.

Drop the existing Index with does not allow duplicates:

alter table porders drop ix_porders

Re-create the index without duplicate contraint:

CREATE NONCLUSTERED INDEX ix_porders ON porders(Numbered)