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

Import External Data From Access – Northwind

forums › forums › SQLyog › Using SQLyog › Import External Data From Access – Northwind

  • This topic is empty.
Viewing 2 reply threads
  • Author
    Posts
    • November 23, 2009 at 12:11 pm #30052
      peterlaursen
      Participant

      I am not sure if I understand.  Do you think there is an issue in SQLyog we should look into? If so please specify?

    • November 23, 2009 at 12:43 pm #30053
      ken
      Member
      'peterlaursen' wrote on '23:

      I am not sure if I understand.  Do you think there is an issue in SQLyog we should look into? If so please specify?

      Thanks, Peter.

      I think that I had two problems. The secondary one may have been my old ODBC driver for MySQL, but maybe that wasn't a factor at all.

      The primary issue was that somehow, the Query objects from my Access db, which I believe is stock Northwind from Office XP, were getting picked up when I did “Import External Data”. I am new to this feature, so I was lazily selecting “Select All”, which included the Queries. When I got the message “Query Support Unavailable”, I didn't know whether that referred to MySQL (it was late). At that point, nothing was working.

      The first thing I got working was a Where clause of 1=1, with the Select * from Products, which added records to the database, but in the table Results. So there was hope.

      Next, I selected just the first 3 tables, which worked.

      Then, I went back and selected the other 6 or so tables, which worked.

      It turns out that the problem was the Access queries being checked/selected.

      If there is a defect in SQLYog, perhaps it should not offer Query objects for import. Maybe this is a function of the Access version, I don't know.

      I am attaching the database, if you would like to try to replicate–ooops, Error The server returned an error during upload. Anyway, you can easily find this file, probably.

      Best,

      Ken

    • November 24, 2009 at 8:51 am #30054
      peterlaursen
      Participant

      OK – now I understand the meaning of “Query Support Unavailable”. It is the Access VIEW-like 'saved query' causing problems here.  Actually we can import a VIEW from most ODBC-sources to a MySQL table (provided that the driver exposes VIEWs), but not an Access 'saved query'. I think you are right that we should not show those or not check those as default.

      We will discuss how we can make the interface more clear in this respect.

  • Author
    Posts
Viewing 2 reply threads
  • You must be logged in to reply to this topic.