SOLVED

Export to text wizard failing

%3CLINGO-SUB%20id%3D%22lingo-sub-1605409%22%20slang%3D%22en-US%22%3EExport%20to%20text%20wizard%20failing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1605409%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%20simple%20query%20(query1)%20that%20I%20want%20to%20export%20as%20csv%20text%20file.%20I%20am%20using%20a%20method%20I%20used%20successfully%20int%20he%20past%20but%20this%20time%20when%20I%20try%20it%20fails%20and%20reports%3C%2FP%3E%3CP%3E%3CFONT%20color%3D%22%230000FF%22%3E%22%3CSPAN%3ET%3CFONT%20size%3D%222%22%3Ehe%20Microsoft%20Access%20database%20engine%20could%20not%20find%20the%20object%20'Query1.txt'.%20Make%20sure%20the%20object%20exists%20and%20that%20you%20spell%20its%20name%20and%20the%20path%20name%20correctly.%20If%20'Query1.txt'%20is%20not%20a%20local%20object%2C%20check%20you%20network%20connection%20or%20contact%20the%20server%20administrator%3C%2FFONT%3E%22%3C%2FSPAN%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThis%20error%20indicated%20I%20don't%20have%20write%20access%20to%20save%20the%20file%20or%20I%20am%20using%20an%20invalid%20file%20name%2C%20but%20I%20am%20not.%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ENotably%2C%20when%20I%20follow%20the%20wizard%20but%20select%20the%20option%20%3CFONT%20size%3D%222%22%20color%3D%22%230000FF%22%3E%5Bexport%20data%20with%20formatting%26nbsp%3Band%20layout%5D%3C%2FFONT%3E%26nbsp%3BI%20can%20choose%20the%20same%20filename%20and%20location%20(which%20is%20my%20local%20drive)%20and%20it%20will%20write%20the%20file.%20But%20this%20output%20format%20is%20not%20CSV%20format%20I%20want.%20However%20when%20I%20do%20select%20this%20option%20I%20do%20get%20a%20popup%20asking%20me%20%22encode%20query1%20as%22%20and%20a%20choice%20of%20radio%20buttons%20to%20select%20the%20file%20encoding%20type.%20I%20do%20not%20get%20this%20option%20offered%20when%20I%20use%20the%20normal%20export%20method%2C%20and%20I%20believe%20in%20the%20past%20I%20did.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAs%20a%20work-around%2C%20I%20use%20the%20export%20wizard%20to%20out%20put%20it%20as%20an%20excel%20file%2C%20the%20in%20excel%20save%20it%20as%20CSV%20without%20issue.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20tried%20closing%20and%20opening%20access%20and%20creating%20a%20new%20database%20with%20just%20the%20one%20table%2C%20but%20get%20the%20same%20issue.%20I%20am%20guessing%20there%20is%20some%20corruption%20or%20setting%2C%20but%20have%20no%20idea%20how%20to%20progress%20to%20a%20solution%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1605409%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAccess%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1606771%22%20slang%3D%22en-US%22%3ERe%3A%20Export%20to%20text%20wizard%20failing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1606771%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F669139%22%20target%3D%22_blank%22%3E%40drareve%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22...%3CSPAN%3E.%20I%20am%20using%20a%20method%20I%20used%20successfully%20int%20he%20past....%22%3CBR%20%2F%3E%3CBR%20%2F%3EWhich%20method%20is%20that%3F%20Knowing%20that%20detail%20could%20help%20someone%20think%20of%20a%20useful%20suggestion%20to%20try.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1607747%22%20slang%3D%22en-US%22%3ERe%3A%20Export%20to%20text%20wizard%20failing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1607747%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F126074%22%20target%3D%22_blank%22%3E%40George%20Hepworth%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20access%20to%20another%20PC%20where%20it%20works%20as%20expected.%20The%20steps%20are%3A%3C%2FP%3E%3COL%3E%3CLI%3EFrom%20Access%20GUI%3A%20Right%20click%20query%2C%20select%20export%20%26gt%3B%20text%20file%3C%2FLI%3E%3CLI%3EDefine%20text%20file%20location%20and%20name%20(e.g.%20query1.csv).%20Do%20not%20tick%20boxes%20for%20Export%20data%20with%20formatting%20and%20layout.%20Select%20OK%3C%2FLI%3E%3CLI%3ESelect%20radio%20button%20%E2%80%9CDelimited%E2%80%9D%2C%20then%20Next%3C%2FLI%3E%3CLI%3ESelect%20radio%20button%20%E2%80%9CComma%E2%80%9D%2C%20then%20Next%2C%20tick%20box%20%E2%80%9Cinclude%20Field%20Names%20on%20First%20row%E2%80%9D%20and%20dropdown%20Text%20Qualifier%20as%20%E2%80%9C%3C%2FLI%3E%3CLI%3EOn%20export%20to%20file%20prompt%2C%20reconfirm%20the%20same%20filename%20as%20specified%20in%20(2-)%2C%20select%20%E2%80%9CFinish%E2%80%9D%3C%2FLI%3E%3CLI%3EDon%E2%80%99t%20tick%20box%20%E2%80%9CSave%20Export%20steps%E2%80%9D%2C%20select%20%E2%80%9CClose%E2%80%9D%3C%2FLI%3E%3C%2FOL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1607754%22%20slang%3D%22en-US%22%3ERe%3A%20Export%20to%20text%20wizard%20failing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1607754%22%20slang%3D%22en-US%22%3E%3CP%3EI%20had%20not%20tried%20rebooting%20the%20PC.%20On%20doing%20so%20the%20issue%20went%20away.%26nbsp%3BI%20should%20have%20tried%20earlier%2C%20it%20would%20have%20save%20a%20lot%20of%20time.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESorry%20this%20action%20has%20removed%20any%20chance%20of%20diagnosing%20the%20root%20cause%2C%20but%20the%20issue%20is%20now%20resolved.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

I have a simple query (query1) that I want to export as csv text file. I am using a method I used successfully int he past but this time when I try it fails and reports

"The Microsoft Access database engine could not find the object 'Query1.txt'. Make sure the object exists and that you spell its name and the path name correctly. If 'Query1.txt' is not a local object, check you network connection or contact the server administrator"

This error indicated I don't have write access to save the file or I am using an invalid file name, but I am not.

 

Notably, when I follow the wizard but select the option [export data with formatting and layout] I can choose the same filename and location (which is my local drive) and it will write the file. But this output format is not CSV format I want. However when I do select this option I do get a popup asking me "encode query1 as" and a choice of radio buttons to select the file encoding type. I do not get this option offered when I use the normal export method, and I believe in the past I did. 

 

As a work-around, I use the export wizard to out put it as an excel file, the in excel save it as CSV without issue. 

 

I tried closing and opening access and creating a new database with just the one table, but get the same issue. I am guessing there is some corruption or setting, but have no idea how to progress to a solution

 

 

 

 

3 Replies
Highlighted

@drareve 

".... I am using a method I used successfully int he past...."

Which method is that? Knowing that detail could help someone think of a useful suggestion to try.

 

Thanks.

Highlighted

@George Hepworth 

I have access to another PC where it works as expected. The steps are:

  1. From Access GUI: Right click query, select export > text file
  2. Define text file location and name (e.g. query1.csv). Do not tick boxes for Export data with formatting and layout. Select OK
  3. Select radio button “Delimited”, then Next
  4. Select radio button “Comma”, then Next, tick box “include Field Names on First row” and dropdown Text Qualifier as “
  5. On export to file prompt, reconfirm the same filename as specified in (2-), select “Finish”
  6. Don’t tick box “Save Export steps”, select “Close”

 

 

Highlighted
Best Response confirmed by drareve (Occasional Contributor)
Solution

I had not tried rebooting the PC. On doing so the issue went away. I should have tried earlier, it would have save a lot of time.

 

Sorry this action has removed any chance of diagnosing the root cause, but the issue is now resolved.