Docmd.TransferText Spec File Not Found

[Patrick.Grant01]

I am running this piece of code:

strSpec = "Import-ValueGrowth"
DoCmd.TransferText acImportDelim, strSpec, "tblValueGrowth", strFileName

and I am getting an error message saying "Run Time Error 3265 - The Text File Specification Import-ValueGrowth does not exist etc"



But the file spec does exist, it is spelt correctly etc.

Any ideas, anyone?? This is a mystery....

A Few more things possibly related:
>>> Tried to delete and recreate specification, repair db, reinstall Office - no luck
>>> Tried to create a Macro - and there are no actions after those beginning with S. (e.g. No Transfer Text action showing for a Macro...)

[ajetrumpet]

did you possibly save it in the exports dialog instead of the imports?

[Patrick.Grant01]

Adam
Thanks for your reply. It is definitely saved in imports. As far as I can tell, it is a Text File specification.

I have seen other reports of what appears to be the same problem with a solution that would skip the problem. ( I mean -Introduce an Error Handler and RESUME NEXT ..... )

[ajetrumpet]

isn't the import spec arg optional? you could leave it out, and just go with the default import operation that access runs.

the other thing is, are you sure the spec you saved was a delimited import? that might be a problem too. it might be a problem if it was saved as like a fixed-width import or something like that.

I don't know much about this, so I can't offer much more.

[Patrick.Grant01]

I have tried all these options without any positive result. I have the impression this is something to do with the installation of Office - but I have not been able to find any installation logs that might help. Nor have I managed to find any Windows events that give me a clue.

isn't the import spec arg optional? you could leave it out, and just go with the default import operation that access runs.

the other thing is, are you sure the spec you saved was a delimited import? that might be a problem too. it might be a problem if it was saved as like a fixed-width import or something like that.

I don't know much about this, so I can't offer much more.

[eelo]

Having exact same problem and would like to learn of fix.
The work-arounds suggested will not work in my case, because using the defaults results in an invalid import. The import works correctly with the saved specification, but I can't use that spec programmatically via 'docmd.transfertext'.

My only other thought is that specification syntax is incorrect, but I didn't see a working example in Help. To help eliminate syntax as the culprit, can anyone confirm that they've gotten this to work with a tab-delimited text file in Access 2010, and if so, provide relevant code?

[domwild43]

Having exact same problem and would like to learn of fix.
The work-arounds suggested will not work in my case, because using the defaults results in an invalid import. The import works correctly with the saved specification, but I can't use that spec programmatically via 'docmd.transfertext'.

My only other thought is that specification syntax is incorrect, but I didn't see a working example in Help. To help eliminate syntax as the culprit, can anyone confirm that they've gotten this to work with a tab-delimited text file in Access 2010, and if so, provide relevant code?

Yeh im having the same problem, although mine has worked

DoCmd.TransferText acImportDelim, strSpec, "COTUpload", objF1.Name, True

but tends to not work most of the time, the problem is with the specification and it wont pick it up. im not sure if anyone has resolved this at all?

[domwild43]

Hi yes if it is the same problem as what I had, you need to save as the spec via the import wizard but on the advance settings box. once you have saved it there you can close the import process and go back to your docmd.transfertext and reference your spec in there in "'s

(im not sure if you were doing what I did, were I thought I was referencing the spec by just referencing the wizard upload?)

DoCmd.TransferText acImportDelim, "COT_Upload", "COTUpload", objF1.Name, True