Project compilation, extended latin support, Access database format conversion (.mdb to .accdb)

[Adam-Ratajczak]

Hi Himself!
I'm an intern from small Polish technological company. This is great repo and I wanted to use it for conversion between two Access jet file standards. But I wanted to ask you about several things.

First of all, I tried to compile it on my workstation, but I couldn't find some of dependencies needed for compilation (especially database management related), I don't know where can I get them.

Second of all, SQL exports seems to not support extended latin and unicode characters, which ofc occurs in some European languages. I think I could fix this, but I need to be able to compile the program.

And last but not least, and also corelated with compilation issues. I think you don't provide Access database formats conversion. I don't ask you to do it. But you could help me with my compilation problems. When I will be able to compile it, I will fork your repo and if I finish making conversion utility, I will send pull request.

Best Regards
Adam

[tecdoc-ukr]

Regarding your message that jet-tool does not support extended Latin, I disagree. At all, it is not correct to speak like that. jet-tool export text data as it is stored in Access (this is checked for ANSI code page).
For example, I correctly export text in the Japanese (932) and cp1252 code pages. All are correct.

[himselfv]

@Adam-Ratajczak Regarding dependencies/compilation issues, sure, post the specifics and I might be able to help.

Regarding unicode, it should be supported, but there's a lot of things that can break Unicode when working from console. E.g. if you're passing data through the console at any point (e.g. cmd1 | cmd2 >file.txt), it might or might not get mangled by your default console output codepage. Try exporting directly through --stdo. Anyway, if you still have problems with the latest versions, give some examples.