executable problems

[tigz]

when i compile any vb projects and tru running it on any other computer (only ones without vb installed I think), i get a missing dll error. for msvbvm60.dll. But it only happens when i use the API.

Does anyone know a way round this cos i don't want to have to be copying dll's with my *.exe's.



thanks

[The Hobo]

Unfortunately, Visual Basic is very dependent on...dependencies, such as .dll's and .ocx's. There isn't any work around, except for expensive programs that bind the dependencies to the exe and decompress them at run time.

[tigz]

do you know how i can get a list of what dll's my *.exe will need at runtime on windows platforms?

Without having to test it on all windows platforms. That dll i mentioned in my initial thread, it sounds like its a specific visual basic dll (msVBVM 60.dll). Why does windows need a VB virtual machine dll - i dont know much about exe's but i thought it was in object code and so was platform specific?

thanks

[The Hobo]

Most of the code used in a Visual Basic program, all those functions like Split, Mid, Instr, etc are stored in a .dll, rather than built into the program itself. All Visual Basic programs generally require msvbvm60.dll to run, and any other .dll file whose code was use within the program.

This is a main reason why C++ programs are bigger than a Visual Basic program that does the same thing.

[jim mcnamara]

If you use the Package & deployment Wizard that comes with VB it will pack up all of the files you need into .CAB files, create a SETUP.EXE file to run it. It also creates a file called system.lst that shows all of your dependencies.