I think I'm MEMORIZING the MySQL docs, trying to hunt this down. :-)
Originally posted by seanf
Other people have posted problems with MySQL on win 2000 here, but typically I can't find you a good example! Have you tried looking at the MySQL website? Are you using mysqld-nt?
This message was moved, but it's not PHP, it's ASP, so I'll probably try asking in that forum (don't hesitate to answer here, though--I'll definitely read your reply!).
I think I've narrowed the problem down: It seems to be caused by an insert statement not properly closing the database. At any rate, this is from the MySQl Manual:
This is what I get if I do an insert into the table that's getting corrupted, then do a "CHECK TABLE tab_customer;" within a few seconds afterward.
If you get the following warning from CHECK TABLE or myisamchk:
# clients is using or hasn't closed the table properly
this means that this counter has come out of sync. This doesn't mean that the table is corrupted, but means that you should at least do a check on the table to verify that it's okay.
When that happens, queries subsequently run against the table return errors.
Here's the code I'm using to do the record insert. It's pretty straightforward (the code block is actually created by MacroMedia UltraDev:
...where (of course) MM_editConnection is the connection string and MM_editQuery is the SQl statement that handles the insert.
Set MM_editCmd = Server.CreateObject("ADODB.Command")
MM_editCmd.ActiveConnection = MM_editConnection
MM_editCmd.CommandText = MM_editQuery
Data IS being correctly inserted. So, why wouldn't the table get closed properly?
Thanks for any help that any of you MySQL masters might give!