List:MySQL ODBC« Previous MessageNext Message »
From:Christian Mack Date:August 11 1999 5:28pm
Subject:Re: Access 97 and MyODBC (Agh!)
View as plain text  
Ram Rajadhyaksha wrote:
> 
> I'm getting the same problems as everyone else with Access 97. The "can't
> do blah blah because you and another user are attempting to change the same
> data at the same time".
> 
> Here's my table:
> 
> +------------+---------------+------+-----+---------+----------------+
> | ID         | int(11)       |      | PRI | 0       | auto_increment |
> | COUNTYCODE | char(3)       | YES  |     | NULL    |                |
> | COUNTY     | varchar(255)  | YES  |     | NULL    |                |
> | TIMESTAMP  | timestamp(14) | YES  |     | NULL    |                |
> +------------+---------------+------+-----+---------+----------------+
> 
> ...I think it is configured correctly to use in Access.
> 
> I'm really bummed that everyone is having this problem. MySQL totally rocks
> but without a problem-free ODBC driver, it's not nearly as useful. :-/
> 
> Thanks,
> 
> --Ram

Hi Ram

First make your TIMESTAMP field NOT NULL.
Then check, that you have set the MyODBC options:
Don't optimize column width
Return matching rows

This should be sufficient

Tschau
Christian

Thread
Access 97 and MyODBC (Agh!)Ram Rajadhyaksha11 Aug
  • Re: Access 97 and MyODBC (Agh!)Steve Lawrence11 Aug
  • Re: Access 97 and MyODBC (Agh!)Christian Mack11 Aug
    • Re: Access 97 and MyODBC (Agh!)Ram Rajadhyaksha11 Aug
      • Re: Access 97 and MyODBC (Agh!)mstarke11 Aug
      • Re: Access 97 and MyODBC (Agh!)Ralph Graulich11 Aug
        • Re: Access 97 and MyODBC (Agh!)Ram Rajadhyaksha12 Aug
          • Re: Access 97 and MyODBC (Agh!)Paul DuBois12 Aug
  • Re: Access 97 and MyODBC (Agh!)Steve Lawrence11 Aug
  • Access 97 and MyODBC (Agh!)Michael Widenius17 Aug
  • Re: Access 97 and MyODBC (Agh!)Patrick Sherrill17 Aug