[RESOLVED] Corrupted form

[WoF]

Same problem again? All positions snapped to zero?
Please check if the msvbvm60.dll has propably changed again and try to replace it with a good one again.

The bas module you attached loads perfectly into VB IDE and is completely readable.

Maybe other runtime files have got a bug, too, although I can hardly imagine how that could've happened.
I recommend to download vbrun60.exe from microsoft support:
http://support.microsoft.com/kb/192461
It reinstalls msvbvm60.dll and related runtime files. See what happens then.

[DataMiser]

The smile is completly gone.
Same problem again.
I found a verry strange thing.
There is a module in my project call mdlAlgemeneSubs. (enclosed)
When i open it with a texteditor the text is complete.
However, when i open it in VB6 there is only one line.(enclosed AlgSubsText1)
What happens here and why?
Regards,
Herman

It is normal to see only the first line in this sub with the view settings that you have applied. Notice the two icons in the bottom left corener one shows only the current procedure the other toggles to full module view.

If I open the module on my system I see the same thing as in your picture but if I click the other view I see more code, also if I click the drop down on the right I see several procedures regaurdless of view settings.

[DataMiser]

As for the other problem. If it went away for a little while after you put on a different vb6 vm but then came back I would suspect some malicous software. I would get that copy form your son again place it in a different folder and run FC on it to see if the one in your system folder is still the same as the one from his system. If they are now different then I would strongly suspect a malicous program which would attack the VB runtime although I have never heard of such a program.

If they are the same then it would seem that the problem was/is not in the runtime file.

Reinstall of OS and VB should have fixed pretty mush any kind of problem [assuming it was a clean reinstall] The problem appearing on a second computer with even a different OS is really odd, It is hard to say without knowing what else is on your system as it could be a problem with your install files or there could be some other software on the system that is the cause of the problem.

When you reinstalled did you format first? Did you try vb before appling the service pack(s)? Did you try to register the VB6 runtime? Have you checked your system to see if there are any other copies of the VB6 runtime located in another location?

[Broozzzbud]

Hi, let me step in also,
I'am herman's son.

Strange things heappen there. I did a fresh install windows xp home, installed sp3, then installed vb6 from the cd. installed sp5 and 6. Then everthing worked fine and we wend home again.

Also installed it on a 64 bit win 7 home premium, this pc had the same problem, however the virtual xp pro i raised on this machine doesn't gif the problems.

What is weird is that when the proble occurs, also the coordinates and size displaed in the top bar don't function.

Last resource, we installed yesterday a finished project with the runtime files.

Then it functioned again. Today it doesn't anymore, i beleive there is a restore cd pushed into the old machine now.....

[dglienna]

Might be a permission problem, or even some rouge AV product.

[Broozzzbud]

what do you meen a antivirus i asume or grahpics card

[WoF]

The most interesting thing at the moment is:
Is there something modifying the runtime files?
Do as proposed. Copy the good msvbvm60.dll into a spare folder and copy it over the actual file in system32. This remedied the problem once, as you explained.
Then wait until the error pos up again and compare the runtime with the spare file if it has been changed.
Also I recommend again to get the other runtime files from microsoft, too, and see if they are the same on your problem machine.

[HermanTabbert]

I believe that my son found the problem.
On form load i set the decimal sign to . (point) and the thousand seperator to "".
Something there went wrong and the decemal sign was set to "" in the register.
When the form was corrupted and we were looking in the register the indeed was a "" as decimal seperator.
When we changed the decimal sign into a "." (point) and started VB again it all was running ok.

An other question is also:
When the customer computer says the decimal sign is a "," (comma) (How can i see that) and how can i change that in the register into a "." (point).
And of course set it back when closing mij program.

[WoF]

Wow. This is most interesting. Your son seems to be a good spotter. Well done.

In the office I work with a german XP which has the decimal sign as "," and the thousands separator as "." and I never run into a problem. It seems VB usually does not care for the regional settings of these constants, except you explicitly define so.

[dglienna]

What OS are you using? Vista+ should be able to adjust the Regional Setting, I think

[HermanTabbert]

On the machine with the ex-problem, the OS is XP home edition.