×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Many of the "cool" reporting tools require a bit of set up. This may
include:
- Field renames,
- Joining the tables together
- Calculating fields, like BPCS on hand
and much more.
I'd argue that if this is the main reason that a "cool" tool appeals to
you the unleash the hounds. Turn your developer loose and tell them to
create some decent views. After all wouldn't this:
create view rob/iimV01 as
select iprod as itemnbr,
iopb+iadj+irct-iiss as OnHand
from iim
where iid='IM'
simplify a query down to
select itemnbr, onhand from iimV01
And for a user to have a simple query like
select * from rob/openorders
order by daysdue
All you have to create is a decent view like
create view rob/openorders as
select hord as orderno,
hcust as customer#,
hcpo as custPO#,
lline as line#,
lprod as itemnumber,
lqord-lqshp as ordbalance,
numtodate(lrdte) as requestdBy,
days(numtodate(lrdte)) - days(current date) as daysdue,
idesc as itemdesc,
iclas as itemclass
from (gdidivf/ech left outer join gdidivf/ecl
on ech.hord=ecl.lord) left outer join
gdidivf/iim
on ecl.lprod=iim.iprod
where hid='CH' and lid in('CL', 'CS', 'LI') and iid='IM'
Doesn't that beat the snot out of redoing that logic in every Query?
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.