Results 1 to 7 of 7
  1. #1
    4 Star Lounger
    Join Date
    Jun 2001
    Location
    Sacramento, California, USA
    Posts
    491
    Thanks
    0
    Thanked 0 Times in 0 Posts

    RUNTIME 3709 (Access 2003)

    My IT people are always so secretive when they upgrade, or put patches etc.

    What would cause a Runtime 3709 "The search key was not found in any record" error when importing a text file using the same specs I have always used?

    I have a form with the following code:

    DoCmd.TransferText acImportFixed, "IMPORT SPECS 2009", "ELIGIBILITY", _
    "R:XYZ HMOS 2009ABCDE 2009JAN 2009Text FilesCN15_122508_H1000E_Elig.txt", False, ""

    Nothing has changed within the database itself and IT says nothing changed with the network.

    Any suggestions? I cannot import the files manually either. (The search key cannot be found in any record)

    Thank you for helping.

    Michael

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: RUNTIME 3709 (Access 2003)

    Does the destination table contain a memo field? If so, MSKB article Error message when you enter a large amount of text in a Memo field that contains an index in Access: "Run-time error '3709'" might apply.

  3. #3
    4 Star Lounger
    Join Date
    Jun 2001
    Location
    Sacramento, California, USA
    Posts
    491
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: RUNTIME 3709 (Access 2003)

    I just did a search and have some more info:
    There are no memo fields
    I am using a back end database
    I created a new database from scratch
    Compact & repair did not work

    I have no problem importing other tables into other databases, which normally would lead me to believe it was
    the particular database. But I have created a new one from scratch and still get the error.

    Thanks for any input.

    Michael

  4. #4
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: RUNTIME 3709 (Access 2003)

    Have you checked the text file for invalid data?

  5. #5
    4 Star Lounger
    Join Date
    Jun 2001
    Location
    Sacramento, California, USA
    Posts
    491
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: RUNTIME 3709 (Access 2003)

    Well, although there were no ?Memo Fields" in the file, the next to last field is a "FILLER" (text) field of 297 characters.

    When I checked off the box to "Skip" importing that field, the import went fine.

    So I guess "large text field" is similar to a memo field in this instance.

    All is well again in Sacramento..

    Thank you Hans !

    Michael

  6. #6
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: RUNTIME 3709 (Access 2003)

    Ordinary text fields have a maximum length of 255 characters, so 297 characters won't fit in a text field.

  7. #7
    4 Star Lounger
    Join Date
    Jun 2001
    Location
    Sacramento, California, USA
    Posts
    491
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: RUNTIME 3709 (Access 2003)

    Makes sense, of course !! Thank you Hans !

Posting Permissions

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