| Subject | Re: OLE Unknown error: 8007:0057 |
| From | duncan mackay <dulcalma@bigpond.com> |
| Date | Fri, 11 Apr 2025 19:28:45 -0400 |
| Newsgroups | dbase.getting-started |
duncan mackay Wrote: > Mervyn Bick Wrote: > > > On 2025/04/10 12:07, Mervyn Bick wrote: > > > > > I don't use Windows 11 but with dBASE 2019 13.20Â b2618 (11/26/2019- > > > EN191126) and Windows 10 Pro, 64-bit, version 22H2 the attached example > > > gives the correct answers. > > > > > > Mervyn. > > > > Web-News doesn't display chr(0xF0) properly but the code in the example > > program should be OK. > > > > Mervyn. > > Hi Mervyn > > Thank you for noticing the "\xfo" instead of "\xf0"; I checked up with the backup and it is > a case of chronic finger droop where unknowningly I have hit the o key at exactly the wrong place > > I tested your code (thank you) but it did not show any errors; however if I changed it to hex the > error came up. > > If I used chr(240) as the test pattern on your code; there was no error > > I tried the program with "ð" as the test pattern but it came up with the same error. > I modified the program to use := but it came up with an error as being not allowed > > I recently read in another program's news group that Microsoft that it had changed its scripting > language. ? the problem > > I am wondering if it is a bug > > Regards > duncan > > Hi Could not get to it yesterday but it also occurred with several other hex numbers > 127. However using the same library with other .prgs that use the same library there were no troubles I am not sure if the offending hex codes were in the input files as they are just represented as a "?". Will investigate further next week Duncan | |