Printable View
Hello guys..
This is the 1st time something like this has happened to me, but having made my own custom activex control works and behaves fine when its run from VB, but when i compile it things get messy !!!
A position problemming..!!!
What could cause this..?
Define "messy".
well basically.. when ran through VB the activex control i did was functioning fine.. no error at all...
but when i did a test compile to .exe
it seems like it was picking any positioning codes: for eg. if a shape had to be in a certain position, it wasnt,, the size was off.. etc... it was reading its properties.. dont know but it only happened when compiled to .exe!
and having spent the whole day nearly trying to fix. it.. and i managed to sort it out..by adding extra properties n stuff.. to manage a few things...
but still weird.. why did vb debugger show stuff fine but compiled not..!!
Compiled machine code isn't the same as the code used in IDE. Under IDE you use interpreted p-code (to what you can also compile your program to), but it is slow. Compiled programs are native code and much faster. There are some cases when compiled is different from IDE: other one may have a bug or there might be slight differences in how memory is organized. Or there can be less error checking in compiled program, which may cause different behaviour in the compiled program.
One reason why being careful with the proper datatypes and checking for valid value ranges is important.