CodePudding user response:
In the DLL?CodePudding user response:
This is likely to have a look at the date of the DLL, whether have the latestCodePudding user response:
381 don't in MID in MIDACodePudding user response:
Before PB10 program calls the same DLL, the return value is correct, the return value is not in the program of PB10. I read the article, a UNICODE and ANSI code in a different way, but I also in accordance with the said in a function declaration alias for "exchangedata; Ansi, the return value or not."CodePudding user response:
The return value is an array, a 381 - bit is the balance of the original, so don't need to use MID/MIDA, 44-52 is a social security card, 53-70 is id card number, 71-100 is a name, gender, 101 is 102-104 is the national code, I defined array is [500]CodePudding user response:
All in all, before upgrading to PB10, credit card can be used all the time, can't be used after the upgrade to the PB10CodePudding user response:
With an array of bytes rather than a char arrayCodePudding user response:
Yes, I went back to try, thank you.CodePudding user response:
Or not, after cannot read card,CodePudding user response:
That's weird, why PB6.5 calls no problem, use PB10.5 call wrong. Looks upgrade is not a good thing, too many problemsCodePudding user response:
It's a pity that I don't have the equipment, otherwise I also want to tryCodePudding user response:
/* * -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --* function: gf_string
* function: solve the problem of Chinese characters garbled
* parameters: as_string original string
* * -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- - */
Return a String (ToUnicode (Trim (as_string)), EncodingANSI!)
This is certainly can
CodePudding user response:
Alias for "exchangedataW try.