Distributing programs programmed in QB64?

[DSMan195276]

just to continue the talking about distribuiting only program with no source code...
If I use also one instruction about sound my code becomes LGPL  and I must share source code
if I use no instruction about sound my code is MIT license
....
if I use a different sound library my code is MIT license plus library's licence.
...
is it right?

I would make a few important distinctions:

One, code you've written can be licensed under whatever license you want, even multiple ones. This is because you own the copyright, and thus the ability to grant use of it via a license.

Two, QB64 itself does not place any requirements on what license you make your code available under, You can choose GPL, LGPL, MIT, Apache 2.0, etc. whatever you want. In particular MIT is not a requirement.

And three, regardless of the license you choose for code you personally wrote, you still have to meet the requirements of the licenses of other code used in your program:

• For the MIT libraries, this means including a notice about the MIT license along with your distributed executable.
  
• For the LGPL sound libraries, you have to meet the requirements of the LGPL, which functionally requires making the source code for the entire program (including your code) available.
  

In either situation, your underlying code does not have to be MIT or LGPL but just has to meet their requirements while using those libraries, and consequently be released under a compatible license. So if you write a program that uses sound and then stop using sound in the future, you would no longer have to meet the LGPL requirements and could stop publishing your source code (assuming you wrote all the code and no other libraries you're using are LGPL).

(Note that things get a bit more interesting if you're creating a library that gets linked into others, but QB64 can't currently produce libraries so it's not that important)