Programming Forums > Application Development > Visual Basic

Lesliect6 · Sep 19th, 2006, 3:49 PM

Hello!

I don't know how familiar you are with this, but I'll give it a try.
I am using the free compiler Envelop Visual Basic, and I want to create a math program. After having succesfully tested it, I wanted to test it on another computer, to see if there were any bugs. I copied a number of dlls required, and when I executed the program I got the error message : "Abnormal program termination." And it won't work. I had the same configuration on the two PCs, all the necessary files were there, yet it doesn't work. The only thing which isn't the same is that the original PC OS is Win XP home, the other Win XP Professional. Could you help me?

Leslie

Ooble · Sep 20th, 2006, 8:14 AM

What DLLs were required? Was it a standard EXE project?

Lesliect6 · Sep 22nd, 2006, 7:30 AM

Thank you Ooble you were right, I did not copy some DLLs to the WINDOWS folder that was the problem! Thaks!

Ooble · Sep 22nd, 2006, 7:51 AM

I was right? I didn't suggest anything. :p

Congrats on fixing the problem.

peace_of_mind · Sep 22nd, 2006, 2:04 PM

Ooble you're a genius.

MBirchmeier · Sep 22nd, 2006, 3:24 PM

Quote:

Originally Posted by Lesliect6

Thank you Ooble you were right, I did not copy some DLLs to the WINDOWS folder that was the problem! Thaks!

I'm not familiar with best practices on DLL's but isn't it better to keep/run them from the executable's directory rather than copying them into the windows directory? It just seems like it's opening up the opportunity for artifacts being left behind on the computer.

-MBirchmeier

DaWei · Sep 22nd, 2006, 3:52 PM

Given the outcome of bad coding and disorganization, it is probably better to keep your own .dll locally. The original idea, though, was to provide code reusability. You could even modify an existing .dll provided that you modified it in such a way that it was backwards compatible (didn't break anything that used it before). It didn't work well. Fortunately, the growth in mass-storage capabilites has allowed us to survive having ten-jillion copies of simple functions.

Sep 19th, 2006, 3:49 PM	#1
Lesliect6 Programmer Join Date: Aug 2005 Posts: 68 Rep Power: 4	Envelop VB runtime error Hello! I don't know how familiar you are with this, but I'll give it a try. I am using the free compiler Envelop Visual Basic, and I want to create a math program. After having succesfully tested it, I wanted to test it on another computer, to see if there were any bugs. I copied a number of dlls required, and when I executed the program I got the error message : "Abnormal program termination." And it won't work. I had the same configuration on the two PCs, all the necessary files were there, yet it doesn't work. The only thing which isn't the same is that the original PC OS is Win XP home, the other Win XP Professional. Could you help me? Leslie

Sep 20th, 2006, 8:14 AM	#2
Ooble I eat cake for breakfast. Join Date: Jul 2004 Location: In my box. Posts: 4,434 Rep Power: 9	What DLLs were required? Was it a standard EXE project? __________________ Me :: You :: Them

Sep 22nd, 2006, 7:51 AM	#4
Ooble I eat cake for breakfast. Join Date: Jul 2004 Location: In my box. Posts: 4,434 Rep Power: 9	I was right? I didn't suggest anything. :p Congrats on fixing the problem. __________________ Me :: You :: Them

Sep 22nd, 2006, 2:04 PM	#5
peace_of_mind Professional Programmer Join Date: Sep 2004 Location: Hell if I know most of the time Posts: 439 Rep Power: 5	Ooble you're a genius. __________________ Amateurs built the ark Professionals built the Titanic

Sep 22nd, 2006, 3:52 PM	#7
DaWei Resident Grouch Join Date: Jun 2005 Posts: 6,453 Rep Power: 10	Given the outcome of bad coding and disorganization, it is probably better to keep your own .dll locally. The original idea, though, was to provide code reusability. You could even modify an existing .dll provided that you modified it in such a way that it was backwards compatible (didn't break anything that used it before). It didn't work well. Fortunately, the growth in mass-storage capabilites has allowed us to survive having ten-jillion copies of simple functions. __________________ Abstraction doesn't make it impossible to write bad code; it makes it possible to write superior code. Contributor's Corner: Grumpy on C++ Exceptions DaWei on Pointers

Sep 22nd, 2006, 7:30 AM	#3
Lesliect6 Programmer Join Date: Aug 2005 Posts: 68 Rep Power: 4	Thank you Ooble you were right, I did not copy some DLLs to the WINDOWS folder that was the problem! Thaks!

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
C# corruption!!!	Kilo	C++	32	May 21st, 2006 9:44 PM
Masm	rsnd	Assembly	4	May 20th, 2006 10:05 PM
libraries	matko	C	1	Jan 22nd, 2006 3:12 PM
Runtime error R6034	Polyphemus_	C++	4	Nov 27th, 2005 6:14 AM
Mono Runtime error.	pr0gm3r	C#	8	Oct 12th, 2005 4:10 PM

Programming Forums > Application Development > Visual Basic

Envelop VB runtime error