what do you meen a antivirus i asume or grahpics card
Printable View
what do you meen a antivirus i asume or grahpics card
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.
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.
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.
What OS are you using? Vista+ should be able to adjust the Regional Setting, I think
On the machine with the ex-problem, the OS is XP home edition.