General discussion


VB Runtime error

By shala.0829 ·
hi.. I'm a beginner of VB.

uhm. Everytime I run the program that includes an object (lets say I created a textbox or a button )the MS Visual basic 6.0 terminates, it shows the send/don't send error report, then the program closes.. I tried sending the report it tells that there's no current solution to the problem.

There's nothing wrong in the installation process. I tried installing the VB in other computer.. it works fine.. it runs!! what's wrong in my system??

please help me..

oh by the way, when printing simple codes like

Print "Hello world!"

in the form..It works fine.. it runs!

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

When you say created a textbox

by Tony Hopkinson In reply to VB Runtime error

Do you mean put one on the form from the tool box palette, or create it programtically.

If the latter, a sample of the code my tell us something.

Oh and why are using vb6 to learn?

VB.Net would be a better choice, surely

Collapse -

hi tony..

by shala.0829 In reply to When you say created a te ...

the one from the tool box pallet.. I was trying to run it without a program or a code associated to it.. but the VB terminates. I tried doing the same thing in other computer, it runs!! I think there's something wrong in my PC.. I just don't know what. I'm not sure.

i am using VB because we have a project in school.. HR Technology Map of every personnel. Our prof. says VB with MSaccess is better than java in handling database.. then we have to network it, 1 comp. would act as a server then let's say the other two are clients..

What do you think?? You think I have to use VB. Net??

Collapse -

No, what you are doing should work

by Tony Hopkinson In reply to hi tony..

If your code works on one pc but not another, there's definitely something different.

Stop struggling with it and get the techs in, if it's a school pc

You don't have to use anything, if you are learning programming, with an eye to a career in it, VB6 is a very bad choice.

It's seriously out of date and designed for the untrained, so it can have you develop all sorts of terrible habits.

Collapse -

haller again!! Thanks but wait.....

by shala.0829 In reply to No, what you are doing sh ...

uhm.. so what language should we pursue in doing the project?? And what about the database and networking?? We have 3 weeks to do the project(the mapping of personnel)..

Collapse -

I can't tell you that from all the way over here mate

by Tony Hopkinson In reply to haller again!! Thanks but ...

Better off talking to the prof. If he indicated vb6 and access was the way to go, then it probably is to get the assignment done, which of course is the objective.

Three weeks is way to little time for you to change direction now.

Collapse -


by shala.0829 In reply to I can't tell you that fro ...

yah I guess you're right.. The deadline is so near.. And to think we also have 7 other subjects that needs our time.. Lots of projects this sem.. huuuhh..

Thanks a lot..

Collapse -

Tony has very good advice

by seanferd In reply to haller again!! Thanks but ...

VB.NET is what you should have been using, but it is way too late now.

I can only suggest that you make sure all necessary VB runtime files are installed on your machine and registered properly.

Collapse -

hi seanferd

by shala.0829 In reply to Tony has very good advice

do you mean the 'vbrun60sp5.exe'?? How can I ensure that it's registered correctly??

Collapse -

Hello there, shala

by seanferd In reply to hi seanferd

I believe that vbrun60sp5.exe is actually the installation file for that runtime. It would need to be run (thus installed). If installed, the file would be VB6STKIT.DLL or similar. I would check in the error report to make sure what the problem file actually is, although that is probably the one.
What I would do is reinstall Visual Basic 6.0 (the IDE) to make sure everything is properly installed and registered. If you want to try registering the file first, you'd do this at a command line (or in the Run box):<br>
regsvr32 /u <i>path to dll</i> <br>
regsvr32 <i>path to dll</i> <br>
This will unregister the dll, then register it. Typing regsvr32 by itself will give you all of the command line options.

Related Discussions

Related Forums