PureBasic Forums - English

Awesome -- thank you!

Well, damn... I thought you were saying your old/new examples above were equivalents.

Do you have any idea what the old CRC32Fingerprint() returned?

So shouldn't these be producing the same string?

New Old

You're right, I only saw the original post. Same thing, though, you just unrolled it a bit in your last as far as I can tell..

Other than the #PB_ASCII I don't see any difference in your example and mine.. Am I missing something there?

Unfortunately that wasn't it (It's an all-ASCII program and I'm using the LTS version for exactly that reason).

Since the original function returned an integer and that's what was stored, and the new version returns a hex string, I'm actually comparing like this :

Str(Val("$"+Fingerprint(@temp ...

So I have some legacy code where some checksums were created using this code ( I think in PB 4.4).

(New Code)
Str(Val("$"+Fingerprint(@temp_kb7,StringByteLength(temp_kb7,#PB_Ascii),#PB_Cipher_CRC32)))

(Old Code)
Str(CRC32Fingerprint(@temp_kb7,StringByteLength(temp_kb7)))

Given the same data ...

I'll grab and test it. I had to shelve the project before because though it compiled with your changes, every time I try to connect to the SQLite DB it crashed before.

Ahhhhh perfect!!!

Thanks freak! I should have mentioned that I tried calling SQLInstallerError_() already.. It returns "C" -- yep, just the letter C.

FWIW, this has *something* to do with Unicode, but I'm not seeing it.

Free beer to the first person to spot it!

Interesting, I get no compilation errors at all but did substitute the values for the constants just to test. Unfortunately no change (SQLConfigDataSource_() just returns zero).

Fig wrote:#ODBC_ADD_DSN equals 4
#ODBC_REMOVE_DSN equals 3
FYI...

ODBC_ADD_DSN should be 1, ODBC_ADD_SYS_DSN should be 4, or at least that's how it's been working for about 14 years in this code.. Likewise REMOVE_DSN is 3, REMOVE_SYS_DSN is 6..

I've tried (and failed) to adapt your AddDSN to my needs.. I can't seem to find a clear explanation as to what changed between 5.3 and 5.4 to cause all the trouble? I cannot use Unicode in my case..

Here are the procedure I'm currently using. Is there anything you know of that can be changed here ...

I'm using 5.44LTS, and cannot use Unicode (for a variety of reasons). 5.1 and 5.2 compiled and used this code just fine but 5.44LTS does not. I've seen several other threads about this but the solution was "use Unicode" -- but I can't in this case.. I'm not entirely sure where the unicode tie-in is ...

Thanks guys!