Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Bad encoded character on connecting HFSQL database #291

Closed
fybo opened this issue Oct 3, 2022 · 2 comments
Closed

[BUG] Bad encoded character on connecting HFSQL database #291

fybo opened this issue Oct 3, 2022 · 2 comments

Comments

@fybo
Copy link

fybo commented Oct 3, 2022

Hi Mark,

Before everything, I want to thank you for all the hard-work you do on creating this useful project.

By the way, we've got an issue on connecting an HFSQL database from Windev by ODBC.
Actually, it runs good on most situations but we've a '�' character replacing every special characters with accent like éêàçèï

In the same time, it is well-displayed with RazorSQL by connecting on the same ODBC connector with the same driver.
Same for another projet on Visual Studio C# with the OdbcConnection class which run properly on connecting to the same ODBC connector with the same driver.

Is there a way to fix that by compiling your code differently ?
Or is that a question of deeper encoding that is not caught in the code ?

I'm running your code under Node v16.15.0.
ODBC Driver is available here : https://pcsoft.fr/st/telec/modules-communs-26/wx26_75p.htm

Best Regards,

Fybo

@fybo fybo changed the title Bad encoded character on connectiong Windev [BUG] Bad encoded character on connectiong Windev Oct 3, 2022
@fybo fybo changed the title [BUG] Bad encoded character on connectiong Windev [BUG] Bad encoded character on connectiong HFSQL database Oct 3, 2022
@fybo fybo changed the title [BUG] Bad encoded character on connectiong HFSQL database [BUG] Bad encoded character on connecting HFSQL database Oct 3, 2022
@kadler
Copy link
Member

kadler commented Oct 3, 2022

Another user found this issue as well and figured out a workaround: #284 (comment)

@fybo
Copy link
Author

fybo commented Oct 3, 2022

Thank you buddy, you saved my day ! @kadler

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants