Query by example fields in Customer Order Entry are limited

unknown

We recently upgraded from Visual Manufacturing 9.0.8 SP4 to 9.0.8 SP7 and have noticed that the available fields in the "Query by example" window are significantly reduced.

Prior to the upgrade we had configured the following fields to search on - Order ID, Customer ID, Customer Name, Status, Site ID, Customer Part ID, Drawing ID, Line No, Order Qty, Unit Price, Part ID, Product Code, Salesrep ID, Entered By, Misc Reference, Create Date.

Now the list is limited to - Order ID, Customer ID, Customer Name, Status, Site ID, Salesrep ID, Create Date.  When you try to edit the columns, those other fields are no longer present to select.

Has the database design changed that much between SP4 and SP7? I hope I am missing something simple and can reconfigure the list.  Any comments or thoughts are most appreciated.

Regards,

Todd Broad

Hills, inc.

charles-hooper

Todd,

As discussed in this VMIUG-TEC thread, starting with Visual Manufacturing 9.0.8 SP5, the where= line in the VMBROWSE.INI file is no longer processed for some Visual Manufacturing modules' Browse windows, including Customer Maintenance.  In those cases, if the VMBROWSE.INI file instructs the Visual Manufacturing module to select from more than one database table, a Cartesian join is executed with the tables in the table= entry (for example, if there are three tables with 100 rows each, 1,000,000 rows will be returned for the Browse window when a Cartesian join is performed on the three tables).

As far as I am aware, the Customer Order Entry module's Browse windows still correctly process the where= line in the VMBROWSE.INI file.

The portion of the 9.0.8 SP7 VMBROWSE.INI file that is of interest begins as follows:
[Customer Orders]
version=42
table=CUSTOMER_ORDER,CUSTOMER
title=Customer Orders
key1=CUSTOMER_ORDER.ID
key2=CUSTOMER.ID
sort=CUSTOMER_ORDER.ID
order=1
where=CUSTOMER_ORDER.CUSTOMER_ID=CUSTOMER.ID

For 9.0.8 SP1, that portion of the file appeared as follows:
[Customer Orders]
version=40
table=CUSTOMER_ORDER,CUSTOMER,CUST_ORDER_LINE
title=Customer Orders
key1=CUSTOMER_ORDER.ID
sort=CUSTOMER_ORDER.ID
order=1
where=CUSTOMER_ORDER.CUSTOMER_ID=CUSTOMER.ID AND CUST_ORDER_LINE.CUST_ORDER_ID(+)=CUSTOMER_ORDER.ID

I quickly tested 9.0.8 SP7, with an Oracle Database back end, using the following change, and found that it seemed to work as it did with 9.0.8 SP1 without producing a Cartesian join:
[Customer Orders]
version=42
table=CUSTOMER_ORDER,CUSTOMER,CUST_ORDER_LINE
title=Customer Orders
key1=CUSTOMER_ORDER.ID
key2=CUSTOMER.ID
sort=CUSTOMER_ORDER.ID
order=1
where=CUSTOMER_ORDER.CUSTOMER_ID=CUSTOMER.ID AND CUSTOMER_ORDER.ID=CUST_ORDER_LINE.CUST_ORDER_ID(+)

Test thoroughly!

Charles Hooper
Senior Software Engineer
Meadville Forging Company