Specification Name

[tgavin]

This code used to work but when I open it in Access 2010, it now wants a Specification Name arguement between the transfer type and the file to export. All I am finding on is that it is the export specs but I have no idea what that means. It won't let me skip the arugument.

DoCmd.TransferText acExport, "rptCitiTextExport", "C:\Documents and Settings\Terri Gavin\Desktop\" & [Forms]![frmMonth]![txtFolder] & "CitiBank Export.xls"

[pbaldy]

That argument has been there for a while (it's in A2k). It's optional, so you should be able to just leave it blank, like:

DoCmd.TransferText acExport, , "rptCitiTextExport", "C:\Documents and Settings\Terri Gavin\Desktop\" & [Forms]![frmMonth]![txtFolder] & "CitiBank Export.xls"

[tgavin]

When I leave it blank, I get "The action or method requires a Specification Name argument." Maybe I had it that way in 2002 or 2003, (I have been going back and forth with 02, 03 and 10 depending on client and computer), but now I am suddenly getting that message.

[pbaldy]

I don't have my machine with 2010 on it handy, so I'll try to look at it later. I can't believe they would have made a specification mandatory. Did I get the extra comma in the right place?

[tgavin]

It is in the right place. I have used this code on several dbs and never had a problem.

The current code that exports this file from the Access 97 db (It was originally written in Access 2 and won't convert higher, plus it's a mess from all the people who have played with it in the last 10+ years)

[tgavin]

Actually the code that is in the Access "rptCitiTextExport", acFormatTXT, network path

It needs to be an asci file for a Citibank upload. Now that code returns "The format in which you are attempting to output the current object is not available." That is why I was trying to use that export code which I use with other dbs that are exporting queries.

Any ideas on any of this???

Thanks