List:General Discussion« Previous MessageNext Message »
From:Joshua J. Kugler Date:July 13 2001 9:30pm
Subject:Re: MyODBC 2.50.37 and Access 2000
View as plain text  
This may be a silly question, but since you didn't state it in your e-mail: 
does each record have a primary key AND a timestamp field?

j----- k-----

On Friday 13 July 2001 01:24, Kevin Smith wrote:
> Hi All,
>
> I've installed MySQL 3.23.39 on my Windows 2000 Pro Server and I am
> currently developing a database using Access 2000 as a front-end to MySQL
> using MyODBC 2.50.37.
>
> I have all my MySQL tables linked as ODBC tables in Access.
>
> When I am inputting data into an Access Form and then save the record, all
> the fields are changed to #DELETED.  The record data is saved I know, but
> why do the fields all change to #DELETED when the record is inserted into
> the MySQL table?  Is there a fix for this, or, it is just the case of using
> ADO to do the insert and just refresh the Access Form to then move to the
> record itself... a bit of a pain though...
>
> Any ideas?
>
> Many thanks,
>
> Kevin Smith
>
>
>
> ---------------------------------------------------------------------
> Before posting, please check:
>    http://www.mysql.com/manual.php   (the manual)
>    http://lists.mysql.com/           (the list archive)
>
> To request this thread, e-mail <mysql-thread79347@stripped>
> To unsubscribe, e-mail <mysql-unsubscribe-isd=as.uaf.edu@stripped>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

-- 
Joshua Kugler, Information Services Director
Associated Students of the University of Alaska Fairbanks
isd@stripped, 907-474-7601
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