-
I get this runtime error after I have compiled my program into an EXE. I burnt the programs EXE file to a CD. Ran it on a seperate PC that didn't have anything about my program on it. I ran the setup, and installed it, and then went to the location it placed the EXE. I opened the EXE file, it ran beautifully, I closed it and tried to go in it again and it wouldn't run. it gave me the Runtime 424 error. I tried uninstalling and reinstalling the program, but no luck. So what can I do to get rid of this error?
-
424 is an error occuring when VB can't create a form because it can't find the specified class name. Forms are actually classes which is why you can do dim form2 as new form1. VB changes the class name to whatever the form's name is automatically. At least that's my understanding of it, so why it's doing that now but didn't before you compiled it I don't know ... unless there's some other information.
The MSDN says this tends to occur when using the Add method (forms.add "Form2") where form2 might not exist. Perhaps you changed a form's name before compiling but didn't change it in the code?
Sorry I couldn't be much help ... perhaps that'll get ya going in the right direction.
------------------
Micah Carrick
http://micah.carrick.com
[email protected]
ICQ: 53480225
-
Below is the complete test from MSDN Help. While it doesn't say anything about it, could your problem be that some portion of your app is still in memory because some object you created was not set to Nothing at EOJ? Or possibly if you Shell or otherwise activate another app, could its "process" (if you have Windows NT you can check for active processes) still be running?
Here's the Help text:
References to properties and methods often require an explicit object qualifier. This error has the following causes and solutions:
You referred to an object property or method, but didn't provide a valid object qualifier.
Specify an object qualifier if you didn't provide one. For example, although you can omit an object qualifier when referencing a form property from within the form's ownmodule, you must explicitly specify the qualifier when referencing the property from astandard module.
You supplied an object qualifier, but it isn't recognized as an object.
Check the spelling of the object qualifier and make sure the object is visible in the part of the program in which you are referencing it. In the case of Collection objects, check any occurrences of the Add method to be sure the syntax and spelling of all the elements are correct.
You supplied a valid object qualifier, but some other portion of the call contained an error.
An incorrect path as anargument to ahost application's File Open command could cause the error. Check arguments.
You didn't use the Set statement in assigning an object reference.
If you assign the return value of a CreateObject call to a Variant variable, an error doesn't necessarily occur if the Set statement is omitted. In the following code example, an implicit instance of Microsoft Excel is created, and its default property (the string "Microsoft Excel") is returned and assigned to the Variant RetVal. A subsequent attempt to use RetVal as an object reference causes this error:
Dim RetVal ' Implicitly a Variant.
' Default property is assigned to Type 8 Variant RetVal.
RetVal = CreateObject("Excel.Application")
RetVal.Visible = True ' Error occurs here.
Use the Set statement when assigning an object reference.
In rare cases, this error occurs when you have a valid object but are attempting to perform an invalid action on the object. For example, you may receive this error if you try to assign a value to a read-only property.
Check the object's documentation and make sure the action you are trying to perform is valid.
For additional information, select the item in question and press F1.
------------------
Marty
