Does anybody has experienced this kind of error? I am using VB6 for development and MySQL as database server. I get this error a lot. And why is it that MySQL database got corrupted? It happens to me many times already. Can not open the file,has to delete it and define the structure again. Anybody pls help! ;-), thanks guys.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
E-Fail Status Error
- Thread starter katana69
- Start date
sleipnir214
Programmer
It's difficult to say. What are you doing to the database.
Also, have you tried the REPAIR TABLE command in MySQL, rather than deleting and recreating the table?
Want the best answers? Ask the best questions: TANSTAAFL!!
Also, have you tried the REPAIR TABLE command in MySQL, rather than deleting and recreating the table?
Want the best answers? Ask the best questions: TANSTAAFL!!
I have had this problem many times when I first started using MySQL/VB... There are MANY factors to why this is happening... If I remember right, it probably has to do with putting the wrong type of data into a mismatched field. As an example, you need to make sure you don't put .08775 into a field that will not accept it... With VB it will add it, and then it could cause problems when you go to read it...
Make sure your fields in MySQL are long enough to accept the data you are trying to enter, and then make sure that in your VB text controls, that you ONLY allow the length on that field to be allowed to be typed in... Putting a longer text field than allowed will also cause funky errors...
I have noticed that if you link the table into access, sometimes you can see the record that has the problem by the #ERROR in the fields/record(s).
You should NOT have to re-structure and define again... Remove the records that are the problem, and it should be back to normal...
Check your formatting of variables; tinyint for checkboxes, int for integer fields, decimal for currency, text for memo fields, etc...
Hope this helps, keep us posted.
Aaron
Make sure your fields in MySQL are long enough to accept the data you are trying to enter, and then make sure that in your VB text controls, that you ONLY allow the length on that field to be allowed to be typed in... Putting a longer text field than allowed will also cause funky errors...
I have noticed that if you link the table into access, sometimes you can see the record that has the problem by the #ERROR in the fields/record(s).
You should NOT have to re-structure and define again... Remove the records that are the problem, and it should be back to normal...
Check your formatting of variables; tinyint for checkboxes, int for integer fields, decimal for currency, text for memo fields, etc...
Hope this helps, keep us posted.
Aaron
- Thread starter
- #4
Guys! Thank you very much for the replies, it helps a lot specially from pcsaaron,thanks man! Yep, I was able to find that out myself making my suspicion correct. I did some investigation on per record basis and i found out about that condition in the fields getting the wrong data types. Right now it is doing fine and I don't have any problem so far.
- Status
Similar threads
