Thanks Chip. I am less concerned about the how as I am happy to manually brute force replace the 200 instances of usage. It's more about whether or not to...
Regards, Narinder Chandi, ToolBox Systems Ltd. -- -----Original Message----- From: Chip Scheide <[email protected]> Date: Friday, 7 June 2019 at 17:02 To: 4D iNug Technical <[email protected]> Cc: Narinder Chandi <[email protected]> Subject: Re: v15 to v17 Conversion of Obsolete _o_C_STRING/_o_ARRAY STRING Commands not the easiest thing to do. what I did: - globally replace: C_String(<size>; -> C_Text( Where <size> is a string size that is used a lot in your system(s). repeat until most of the more often used string sizes are done. - globally replace: C_String( -> C_Text( - Run compiler, fix individual errors, or notice sizes you missed above and do global replaces using C_Text(<size>; -> C_Text( repeat the above for arrays Not fast, but that should resolve the issue - eventually Chip On Fri, 07 Jun 2019 16:48:59 +0100, Narinder Chandi via 4D_Tech wrote: > _o_C_INTEGER I have simply replaced with C_LONGINT as the docs state > that "...4D and the compiler retype Integers into Longints > internally." --------------- Gas is for washing parts Alcohol is for drinkin' Nitromethane is for racing ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
