Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Access 2000 ODBC Import

  • This topic is empty.
Viewing 6 reply threads
  • Author
    Posts
    • #8325
      hoser
      Member

      I'm importing an Access 2000 table and a Date/Time field is ending up as a timestamp field in mysql. That doesn't seems right. 🙁

    • #15470
      peterlaursen
      Participant

      my personal experience is that

      exporting from Access2000 to mysql

      works bettter than

      importing from Access2000 to mysql using sqlyoug

      I don't know if it is a problem with sqlyog og with the ODBC-driver!

      try these steps

      1) use sqlyog to create an empty table in mysql

      2) export the tables from Access

      3) if needed you can alter mysql tables (field lengths etc) afterwards

      I don't know if that solves your problem but give it a try!

      And remember to answer back …

    • #15471
      peterlaursen
      Participant

      correction:

      should have been “create an empty database” not “create an empty table”

      sorry for that!

    • #15472
      hoser
      Member

      Thanks for the feedback..I can work around the problem a couple of ways. The Access->Export to mysql works and a older program I have called mysqlfront does the import correctly. I'm thinking SQLyog should handle the import correctly, so I guess I should submitt it as a possible bug.

    • #15473
      Shadow
      Member

      The ODBC import wizard offers the transform option when you select the tables that are to be imported. The transform option enables you to change the field type to the desired type if the default does not fit your needs, so there is no bug whatsoever.

    • #15474
      hoser
      Member

      I agree it's not a bug. I just think the datetime field should be imported as a datetime…rather than some default that you have to transform back. The desired field type after the import should be the field type I started with, if possible.

      So maybe it falls under the program improvement area?

    • #15475
      Shadow
      Member

      That's a better idea! The best solution could be to allow the users to alter the default field mappings before the import and SQLyog would store the new default types. Agreed?

Viewing 6 reply threads
  • You must be logged in to reply to this topic.