lost the import dll: error 126
Please I need some help I keep getting a message, Import:dll missing or error ect.
it says error 126, but I do not know how to re-install it if I can download it.
답변
- Guessing here: do you have a Declare statement in your program that references "import.dll"? If that is the case, you're working with a 3rd party DLL. You need to put it in a folder so that .NET can find it. Putting it in c:\windows\system32 would certainly work. Putting it in the same folder as your program's .EXE is better...
모든 응답
- Guessing here: do you have a Declare statement in your program that references "import.dll"? If that is the case, you're working with a 3rd party DLL. You need to put it in a folder so that .NET can find it. Putting it in c:\windows\system32 would certainly work. Putting it in the same folder as your program's .EXE is better...
As you mention you are getting Error 126 This sounds like an error message that would be generated by a VB6 based application and not a .NET application.
Are you using VB.NET or and earlier version of VB.
If this question does relate to VB6 then the following applies if your using .NET then you need to provide more information.
These forums are for VB.NET and there are better places to find answers for older versions of VB such as VB6.
Maybe the VB6 newgroups - http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.vb.general.discussion&lang=en&cr=US
or the VB6 resource center
http://msdn.microsoft.com/vbrun/or web sites such as www.vbcity.com
You could however download VB Express and start working with .NET technology - its free to download from microsoft web site.
Hope these point you in the right direction.
- I dunno Stan, VB6 generates error 53 when it can't find the DLL. .NET generates error 0x8007007E which (when properly masked) equals error 126.
As I said, if they arent using vb6 the disregard and preovide more info.
most of .net will display an exception rather than an error code. unless of course you using legacy code which was imported into vb.net or love the on error goto construct and the appropriate error object rather than exception handling.
