Select if NOT Record filename Exists
trevor-linda-weir@att.net
trevor-linda-weir@att.net
Fri, 14 Dec 2001 20:22:52 +0000
George,
Adding to John's logic you can do the following:
Def RepHead char*?? = field of I55first if NOT RECORD
I5531410 Exists else field of I5531410
Trevor
>
>
> John, Kathy, Linda,
>
> Thanks for your response. Two of you have the same idea with the alias but
> there's one
> issue left. If the selection criteria selects 0 records then I have 0 record
> constructs to choose
> from, right? The object is to satisfy the user that the data from their most
> recent run for the
> creation of the I5531410 is indeed present in the file - a sort of integrity
> check in case the
> queues get a bottleneck and someone else runs the create of the file before
> their report
> actually runs (we have multiple job queues). Unless I'm misunderstanding your
> suggestion
> it looks like I'll have to do an extra pass for a cover page or something like
> that. At first I
> thought I'd do 2 passes and create a subfile but if 0 records are selected then
> I'm back
> to square one again anyhow and if that was workable your suggestion of an alias
> would
> be more efficient than 2 passes for sure.
>
> I can't reverse the access order either because the 1st file contains items
> purchased
> against a Bill of Material and the second contains those that have been put on
> the Bill. The
> report cites materials purchased but not yet used on the Bill - so we can catch
> unnecessary
> purchases or exceptions such as contract help - or a buyer running wild doing
> the 'shop till
> you drop' thing.
>
> So unless someone sees something else here I guess I'll go with the cover page.
>
> I appreciate your help,
>
> George
>
>
> |------------->
> |(Embedded |
> |image moved |
> |to file: |
> |pic12984.pcx)|
> | |
> |------------->
> >------------------------------------------------------------------------|
> |"Pickering, John (NORBORD)" <PICKERIJ@norbord.com> |
> |12/14/2001 01:25 PM |
> >------------------------------------------------------------------------|
>
>
>
> To: George J. Wen/NB/USFAC/ABB@ABB_USFAC
> cc: "'Powerhouse List'" <powerh-l@lists.swau.edu>
> Subject: RE: Select if NOT Record filename Exists
>
> Security Level:? Internal
>
>
>
> George
>
> How about:
> >Access I4311 &
> > link PDITM to QAITM of I5531410 optional &
> > link to record(0) of I5531410 alias I55first
>
> Note that some platforms may want "record(1)" instead of "(0)".
>
> Every record complex will have a buffer for I55first assuming the file isn't
> empty. Use the contents of this buffer for headings etc.
>
> Regards,
> JWP
>
>
> > -----Original Message-----
> > From: george.j.wen@us.abb.com [SMTP:george.j.wen@us.abb.com]
> > Sent: Friday, December 14, 2001 1:47 PM
> > To: powerh-l@lists.swau.edu
> > Subject: Select if NOT Record filename Exists
> >
> >
> >
> > Hello List, here's one for you.
> >
> > I'm using the construct for the following access line:
> >
> > Access I4311 link PDITM to QAITM of I5531410 optional
> > Select if Not Record I5531410 exists
> >
> > But what if I want a value from the from I5531410 for printing in the
> > headings
> > even
> > when zero records meet the selection criteria. This value is not
> > presented in a
> > parm anywhere but rather this I55.. file is a work file that is created by
> > the
> > user so
> > it would be useful to see what the first record in the file (one that does
> > not
> > meet the
> > selection criteria) looks like to validate that the correct data (most
> > recent)
> > is there.
> > I could do a cover page report ahead of the main report or something like
> > that
> > but
> > does anyone knows of a "slick and dirty" way or work around?
> >
> > Thank you in advance.
> > George
> >
>
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l@lists.swau.edu
> Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
> Unsubscribe: "unsubscribe" in message body to powerh-l-request@lists.swau.edu
> http://lists.swau.edu/mailman/listinfo/powerh-l
> This list is closed, thus to post to the list you must be a subscriber.
>
>
>