Importing DBF Tables - Sudden 7399 Error

  • Hi i really need help with this problem cause is my job, i use to work every moth with 60 tables dbf with this sql query

    SELECT *  INTO tabla_dbf FROM

    OPENROWSET('MSDASQL','Driver={Microsoft Visual FoxPro

    Driver};UID=;SourceDB=D:\dbftables;SourceType=DBF;Exclusive=No;BackgroundFetch=Yes;Collate=Machine;Null=Yes;Deleted=Yes;','SELECT

    campo1, campo2, campo5, sum(campo6) As campo6 FROM tabla_dbf GROUP BY campo1, campo2, campo5 ')

    in order to import several tables dbf, but suddenly it didn't work, i don´t what happened, it appear the next message

    /*******************************/

    Servidor: mensaje 7399, nivel 16, estado 1, línea 1

    El proveedor OLE DB 'MSDASQL' informa de un error. Memoria insuficiente

    para el proveedor.

    [OLE/DB provider returned message: [Microsoft][ODBC Visual FoxPro Driver]No

    hay suficiente memoria para la asignación de archivos.]

    /*******************************/

    it says something like it doesn't have enouth memory for the provider.

     it doesn't have enouth memory for the file allocation

    I don't know what can i do,

    i work in network of my company there is a admin of window 2000 server, i use sql 2000 (client/ server)

    there are important facts

    1 moth ago. they change my hard disk an

    I used a cleanup program in order to erase temporal files,

    Does anyone can help me please? and what can i do? Please

    sorry about my english

  • Have your tied using a DTS package to import your DBF tables?? I have something similar running as a scheduled task without any problems. Also you might want to try a different dbf driver.

    HTH

    CY

  • This might be similar to what I've seen in the past with AS/400 drivers. There's a limited amount of space for driver code and sometimes these things leak memory and run low. We've had to reboot the server periodically in the past to clear the memory space and then things seem to import fine for a period of time. I believe we were on something like a quarterly reboot schedule.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply