By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,705 Members | 1,845 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,705 IT Pros & Developers. It's quick & easy.

TransferText and Runtime Error 3011 (solved)

P: n/a
Just been having this problem when Exporting a query.

DoCmd.TransferText acExportDelim, "GenMESR Export Specification",
"qryGenMESRExport", 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.
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
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@localhost> wrote in message
news:c2********************************@4ax.com...
Just been having this problem when Exporting a query.

DoCmd.TransferText acExportDelim, "GenMESR Export Specification",
"qryGenMESRExport", 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.

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.