MySQL Bugs: #18911: The database fall by itself (Many, many problems).

Bug #18911	The database fall by itself (Many, many problems).
Submitted:	8 Apr 2006 17:45	Modified:	10 Apr 2006 21:15
Reporter:	Renato Gontijo	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.0.19	OS:	Windows (Windows 2000 Pro)
Assigned to:		CPU Architecture:	Any

Description:
I don't know why, but I had many problems with MySQL 5.0 and MyODBC 3.12.

I report a problem ID 15982.

I have a database with 241 tables. But the the printer function don't work with MySQL, only with Access and SQL Server configuration.
We are studing a way to migrate to PostgreSQL or DB2 Express.

The database is unstable and we having many problems that doen't happen on MySQL 4.1 version.
In version 5.0.16 the erros don't happens but on version 5.0.19 they back to happens.

I use ADO 2.7 (using SQL commands to UPDATE, INSERT AND DELETE).
The tables don't use foreigner keys.

We stunding the possibility to use stored procedures and triggers in project but at this moment we study the possibility to continue using MySQL.

How to repeat:
I don't know.

Suggested fix:
Do some ODBC version that works whit Crystal Reports and Microsoft Solutions like ADO.
I use MySQL since version 3.xx and they NEVER works complete.

Sorry, but you had not added any new information/new bug report here. Only complains (without any repeatable test cases) and description of your future plans. So, I have to mark it as a duplicate of bug #15982 (that bug report really describes some problems with MyODBC and/or software you use with MySQL).

Ok, my apologies... 
If I got a way to repeat the errors I will add another bug, or append to exists bug.