"C K" <[EMAIL PROTECTED]> wrote on 04/07/2006 01:59:39 PM: > On 4/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > > > "C K" <[EMAIL PROTECTED]> wrote on 04/07/2006 01:35:22 PM: > > > > > > > Dear Friends, > > > I have linked tables from MySQL through ODBC DSN in Access 2003. > > > when I go for updating any record in any linked table then it gives me > > > error as follows: > > > Reserved Error (-7776); there is no message for this error. > > > What will be the problem? Please help. > > > Is this error from MS ACCESS or for MySQL. > > > Thanks & Regards, > > > CPK > > > > > > > > > Have you read through this: > > http://dev.mysql.com/doc/refman/4.1/en/msaccess.html > > > > or this: > > http://dev.mysql.com/doc/refman/4.1/en/myodbc-with-vb.html > > > > or checked here: > > http://msdn.microsoft.com/archive/default.asp?url=/archive/en- > us/dnaraccessdev/html/ODC_JetDatabaseEngineVersion30ODBCConnectivity.asp > > (quoted)>>> > > -7776 SQLGetData(SQL_C_TIMESTAMP) Illegal date/time value > > returned. > > <<< > > > > My quick suggestion: Make sure that all of your timestamp and datetime > > fields are within their expected ranges. > I am using MySQL server 5.0.17 and ODBC 3.51.12 for ODBC connection. > When I update an y data from MySQL Administrator or SQLYog it gets updated. >
I see your point? That must be why I *didn't* give you links that document working with MySQL with MySQL Administor OR SQLYog. I gave you links to using MS Access and ODBC with MySQL. Those pages (and the ones they link to) contain valuable information to help you learn how limited those products are compared with MySQL and how you need to adjust your data so that it fits within the boundaries that MS sets for *their* data manipulation tools. The short explanation is that MySQL has more range and capacity than ODBC and Access can handle and you have to work within the MS limits if you want to use with those tools. Shawn Green Database Administrator Unimin Corporation - Spruce Pine
