I have a smart local query and a smart browse that have identical query
statements:

FOR EACH custom.maintreq NO-LOCK,
FIRST symix.notes WHERE symix.notes.key = custom.maintreq.key
OUTER-JOIN NO-LOCK,
FIRST symix.item WHERE symix.item.item = custom.maintreq.item
NO-LOCK:

With this as is, the browse works fine.

Now, I want the browse to only show those records that do not have a
job-closed date. I remember reading in the SL training that you should
never put a where phrase in the smart local query. So I added a where
phrase to the smart browse making it look like this:
EACH tt.tt-maintreq
WHERE tt.tt-maintreq.close-date = ? NO-LOCK,
FIRST tt.tt-notes WHERE tt.tt-notes.key = tt.tt-maintreq.key
OUTER-JOIN NO-LOCK,
EACH tt.tt-item WHERE tt.tt-item.item = tt.tt-maintreq.item
NO-LOCK

When I compile and run this browse, the browse is showing records with
and without close dates but only records that have hits to the notes
table.

I have also tried to use a state set up in the smart local query with
the default state checking the close-date in tt-maintreq with the same
results.

Any thoughts?

Which ADM? ADM(1) OR ADM 2.
As a Progress proffesional this is simple, though I am confused to you
use of local-query

--
mpowell_es
-----------------------------------------------------------------------
mpowell_esq's Profile: http://www.progresstalk.com/member.p...nfo&userid=508
View this thread: http://www.progresstalk.com/showthre...?threadid=8126

Well, I can certainly understand your confusion. Confusion has become
a natural state for me.

I was introduced to progress programming and the SYMIX/MAPICS product
last June. Before that, the majority of my 25 plus year career was
spend working with IBM midrange systems and programming in RPG.

I am trying to learn progress and the SYMIX twists by trial and error,
some old Syteline programming guides, and those kind enough to respond
to my questions posted here and at PEG.com. In particular, I have been
working with the GUI developer, because plans are to update the SYMIX
version to 6.0 which is reported to be more GUI oriented. When this
happens, we want to update our in-house functions to GUI as well.

To answer your question, we are using ADM(1), Symix 4.00 and progress
8.1.

mpowell_esq wrote:
> Which ADM? ADM(1) OR ADM 2.
> As a Progress proffesional this is simple, though I am confused to
your
> use of local-query.

I got it to work.

If you were to ask me how, I probably couldn't give you an answer that
made any sense. That is one of the problems with trial and error. I
am pretty sure that what finally worked this time was something that I
had tried several days ago in one the earliest attempts.

I am going to now go back over my notes, (that is being really
generous), and see if I can't put together some kind of a guide for the
next time.