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

Dbf File Stops Importing

forums › forums › SQLyog › Using SQLyog › Dbf File Stops Importing

  • This topic is empty.
Viewing 4 reply threads
  • Author
    Posts
    • October 6, 2011 at 9:40 pm #12471
      kmccall
      Member

      Just getting the hang of SQLYog. I was happily importing an 8.6 million record dbf file when after more than an hour I got the following message:

      ERROR: [Microsoft][ODBC dBASE Driver] Could not update; currently locked by user '(unknown)' on machine ''.

      The resulting database was only 5,039,916 records. Any ideas what could be causing this?

      Thanks in advance.

    • October 7, 2011 at 7:23 am #32703
      peterlaursen
      Participant

      Well .. it is the driver that runs into the error – not SQLyog. You will probably get same error if you try to load data in another program (Access, Excel) with the same driver.

      Are you sure the file is not in use by another program?

    • October 7, 2011 at 1:52 pm #32704
      kmccall
      Member

      Hm. I did have the database open in MySQL. Is that a problem? But why would it import 5 million rows and then stop?

    • October 7, 2011 at 1:55 pm #32705
      kmccall
      Member
      'kmccall' wrote:

      Hm. I did have the database open in MySQL. Is that a problem? But why would it import 5 million rows and then stop?

      Both times, it stopped at 5,039,916 rows. I was using the Microsoft dBase Driver [*.dbf] It was a dbf exported from SPSS.

    • October 7, 2011 at 6:09 pm #32706
      peterlaursen
      Participant

      It is not a problem that you had a database open in MySQl (from whatever client).. But if the .dbf file was open in another program it could be a problem.

      Since this happens at a specific row this is likely a data specific issue. I don't know what “SPSS” is. But the exported .dbf file could have a problem with specific data. Can you import into Excel/Access or whatever from the .dbf? The error is with the ODBC driver and/or the .dbf file and not with SQLyog definitely! It is the ODBC driver that returns an error.

      If you have an option to export as CSV that may be a solution/workaround.

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