Forum Discussion
Windows or Office 365 Updates on 7/12/22 Introduced Error with TransferText in vba for Access
After the above noted updates I have received several reports of Access error 3125. I have traced this issue to a saved import specification. Below is an example of the error when using an import s...
I think I found the origin of this problem.
In my case, it occurs when the file type is not specified in the import specification.
If file type is 0 in MSysIMEXSpecs, the problem will occur.
As soon as it is set, the problem disappears.
Best
Unfortunately, the FileType was already zero and it still does not work. I've removed TransferText from all my apps and will never use it again. Thanks for the tip though, it did get me into reading more about the MSysIMEXSpecs table.
What I'm saying is that it shouldn't be 0 but a real filetype value (850 for example).
If you use the import wizard and save the format, the type must be filled in, which is not the case when it is 0.- Ah, thanks for the clarification.