M
medu
Guest
those sort of pitfalls should be on psc 'get em fixed' list, the fact that for find/last doesn't care about 'by' clause is simply a bug... most of us know about it (at least those favouring for instead of find/available), we can even document it but this doesn't mean it disappeared 
this is what the doc say on for-each statement "The FIRST and LAST keywords are especially useful when you are sorting records in a table in which you want to display information."... any developer not have been bitten before will fall for that one 
On 04/08/2014 10:00 AM, Lieven De Foor wrote: From: Lieven De Foor Post: RE: For First, For Last, For Each Posted in: OpenEdge Development Link: http://community.progress.com/technicalusers/f/19/p/9396/35972.aspx#35972 The FOR FIRST/LAST behaviour is on our company's list of ABL pitfalls. I've always used FOR EACH... BY, without BREAK, without any problems, so I guess adding it is not needed... -- You were sent this email because you opted to receive email notifications when someone created a new thread. To unsubscribe from: - ...only this thread, disable notifications at http://community.progress.com/technicalusers/f/19/p/9396/35972.aspx#35972. - ...all email notifications from Progress Community, navigate to "Settings", click on the "Email" tab, then under the "Email Configuration" section, set Send Notifications to "No". -- m.edu keep it simple http://www.ganimede.ro http://ro.linkedin.com/in/marianedu medu@ganimede.ro mobile: +40 740 036 212 skype: marian.edu
Continue reading...
this is what the doc say on for-each statement "The FIRST and LAST keywords are especially useful when you are sorting records in a table in which you want to display information."... any developer not have been bitten before will fall for that one On 04/08/2014 10:00 AM, Lieven De Foor wrote: From: Lieven De Foor Post: RE: For First, For Last, For Each Posted in: OpenEdge Development Link: http://community.progress.com/technicalusers/f/19/p/9396/35972.aspx#35972 The FOR FIRST/LAST behaviour is on our company's list of ABL pitfalls. I've always used FOR EACH... BY, without BREAK, without any problems, so I guess adding it is not needed... -- You were sent this email because you opted to receive email notifications when someone created a new thread. To unsubscribe from: - ...only this thread, disable notifications at http://community.progress.com/technicalusers/f/19/p/9396/35972.aspx#35972. - ...all email notifications from Progress Community, navigate to "Settings", click on the "Email" tab, then under the "Email Configuration" section, set Send Notifications to "No". -- m.edu keep it simple http://www.ganimede.ro http://ro.linkedin.com/in/marianedu medu@ganimede.ro mobile: +40 740 036 212 skype: marian.eduContinue reading...