TransferText and Runtime Error 3011 (solved)

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Trevor Best
    #1

    TransferText and Runtime Error 3011 (solved)

    Just been having this problem when Exporting a query.

    DoCmd.TransferT ext acExportDelim, "GenMESR Export Specification",
    "qryGenMESRExpo rt", Environ$("TEMP" ) & "\MESR.CSV" , False

    I get the error 3011 cannot find object 'MESR.CSV'

    Tried using OutputTo, which netted "database or object is read-only".

    Googled this group to find KB article KB225987 for A2K, which refers
    to schema.ini file, which I don't have (A2K2).

    I finally solved it by manually exporting the query and overwriting
    the export specification.

    Just thought I'd say that so it'll be on google for the next person
    with the same problem :-)

    Would be nice if the error message was meaningful, something along the
    lines of the fields in the query don't match the fields in the export
    spec or something? Then I'd know where to look and would have finished
    this report on Friday instead of having to work my weekend :-(

    --
    A)bort, R)etry, I)nfluence with large hammer.
    Tags: 3011 transfertext
    • Wayne Morgan
      #2
      Re: TransferText and Runtime Error 3011 (solved)

      Thank you for letting us know. It is always nice to know what worked so the next person
      can solve their problem.

      --
      Wayne Morgan
      Microsoft Access MVP


      "Trevor Best" <bouncer@localh ost> wrote in message
      news:c22lpv4981 0ghjsef1j7d5mc0 4u3lbpqea@4ax.c om...[color=blue]
      > Just been having this problem when Exporting a query.
      >
      > DoCmd.TransferT ext acExportDelim, "GenMESR Export Specification",
      > "qryGenMESRExpo rt", Environ$("TEMP" ) & "\MESR.CSV" , False
      >
      > I get the error 3011 cannot find object 'MESR.CSV'
      >
      > Tried using OutputTo, which netted "database or object is read-only".
      >
      > Googled this group to find KB article KB225987 for A2K, which refers
      > to schema.ini file, which I don't have (A2K2).
      >
      > I finally solved it by manually exporting the query and overwriting
      > the export specification.
      >
      > Just thought I'd say that so it'll be on google for the next person
      > with the same problem :-)
      >
      > Would be nice if the error message was meaningful, something along the
      > lines of the fields in the query don't match the fields in the export
      > spec or something? Then I'd know where to look and would have finished
      > this report on Friday instead of having to work my weekend :-(
      >
      > --
      > A)bort, R)etry, I)nfluence with large hammer.[/color]


        Comment

        Previous template Next
        Working...