List:General Discussion« Previous MessageNext Message »
From:Dan Nelson Date:July 13 2001 10:41pm
Subject:Re: MyODBC 2.50.37 and Access 2000
View as plain text  
In the last episode (Jul 13), Kevin Smith said:
> Yes, each record has a primary key, but not a timestamp.  Does this
> make any difference?
> 
> This also happens with my Unix machine which has MySQL installed on
> it.  I have had the problem for about a year, but now that I'm
> starting to use MySQL in real-time applications I'm developing at
> work, this is a real bug bear and one that I'm surprised no one knows
> about.

We do know about it, and it's in the manual :)

http://www.mysql.com/doc/M/y/MyODBC_clients.html


     To make Access work:

        * You should have a primary key in the table. If not, new or
          updated rows may show up as `#Deleted#'.

        * You should have a timestamp in all tables you want to be able
          to update.  For maximum portability `TIMESTAMP(14)' or simple
          `TIMESTAMP' is recommended instead of other `TIMESTAMP(X)'
          variations.

-- 
	Dan Nelson
	dnelson@stripped
Thread
INSERT INTO ... SET ...Rolf Hopkins13 Jul
  • Re: INSERT INTO ... SET ...John Birrell13 Jul
  • RE: INSERT INTO ... SET ...Jorge del Conde13 Jul
    • Re: INSERT INTO ... SET ...Rolf Hopkins13 Jul
    • Unsigned data with auto increment => Faster/better... ??David Bouw13 Jul
      • RE: Unsigned data with auto increment => Faster/better... ??Don Read13 Jul
  • RE: INSERT INTO ... SET ...Chris Bolt13 Jul
    • MyODBC 2.50.37 and Access 2000Kevin Smith13 Jul
      • Re: MyODBC 2.50.37 and Access 2000Joshua J. Kugler13 Jul
    • Re: MyODBC 2.50.37 and Access 2000Kevin Smith13 Jul
    • Re: MyODBC 2.50.37 and Access 2000Venu Anuganti13 Jul
      • Re: MyODBC 2.50.37 and Access 2000Sinisa Milivojevic14 Jul
    • Re: MyODBC 2.50.37 and Access 2000Kevin Smith13 Jul
      • Re: MyODBC 2.50.37 and Access 2000Dan Nelson14 Jul
RE: MyODBC 2.50.37 and Access 2000JHDrexler13 Jul
  • Re: MyODBC 2.50.37 and Access 2000Kevin Smith13 Jul
  • Re: MyODBC 2.50.37 and Access 2000Kevin Smith14 Jul