[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: chasing the error...

  • Thread starter Thread starter marian.edu
  • Start date Start date
Status
Not open for further replies.
M

marian.edu

Guest
Replying by email seems to still be broken, at least for me :( Stefan I’m sure I don’t want to run on 10.2B, as said the client seems to be still on 10.1C and update is not an option… 10.2B is the ‘oldest’ instance I’ve could found to play with and that is on Linux :( However, this does consistently GPF on 10.2B/Linux regardless of the date-format. function getDate returns date (strIn as longchar): /* if num-entries(strIn, '-') ne 3 then do: message 'throw' view-as alert-box. return error. end. */ return date(integer(entry(2, strIn, '-':u)), integer(entry(3, strIn, '-':u)), integer(entry(1, strIn, '-':u))). end. define variable dt as date. dt = getDate(‘noc/007-') no-error. On newest version that throws and error for that string because entry 3 is not there. Trying to get around this I’m checking if the string is a somehow valid date by looking at the num-entries and if not valid I need to throw an error so we can catch that later on but then I find that this seems to be an impossible task, uncommenting the block does give me the ’throw’ message but then ‘return error’ statement doesn’t do anything… no error is being thrown when that function is being called, is that a known issue, maybe the expected behaviour? Have to agree it’s hard to be sure how this error handling works lately, you think you got it but then looks like it’s not like that :(

Continue reading...
 
Status
Not open for further replies.
Back
Top