Results 1 to 6 of 6
  1. #1
    Join Date
    Oct 2006
    Posts
    17

    Unanswered: Deter error table creation

    Hi, everyone.

    I prepared a code to import excel data to a table. And its fine. But sometimes occurs errors in the conversion of the data and Access creates a error table report automatically.

    Is there a way to cancel the error table creation like the "Docmd.setwarnings False" option?

    Thanks for help.

  2. #2
    Join Date
    Jul 2009
    Posts
    185
    I would be interested in this as well.

  3. #3
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    What exactly is your code?

    What is the name of the error table?
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  4. #4
    Join Date
    Oct 2006
    Posts
    17

    Standard Error Tables

    Thanks StarTrekker,

    Well, the problem is not related with my code. Even when the wizard import is used a standard table is created always that Access identify a conversion error. Im trying to avoid the automatic creation of this table of errors. Im aware of the errors but they dont matter in my case.

    With the automatic creation of the error table, each time an user run a import a new error table will be created and soon I will full of rubbish !

    So, Im looking to make everything clean.

    Thanks.

  5. #5
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    Ok, so what you would have to do is import the data with VBA and have controls in it to handle (ignore) the data conversion errors rather than relying on Access' importing wizards. The wizards are hard-coded to produce those error tables.

    Or you could ignore them or delete them after your import completes.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  6. #6
    Join Date
    Oct 2006
    Posts
    17

    Ok

    I understood, master. I think I will prefer to try deleting them after the import procedure. I'm not a developer and my skills are very short to try to handle all possible errors in the field conversion.

    Thanks a lot for your help.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •