Access throws Error 3625 - Saying the text file [Import] specification doesn't exist, but it does.

[Papa_Bear1]

Hi,

I have an import specification, that actually works fine both manually and within a VBA loop (executing a DoCmd.TransferText acLinkDelim command) about 3 times around the loop, but then on the 4th round, it suddenly claims the specification doesn't exist.

My first thought was that Access was somehow deleting the spec, but it isn't. The spec is still there (in the MSysIMEXSpecs table).

So - I'm quite stumped here. I have no idea why it would suddenly think it doesn't exist - which it successfully JUST ran three times in a row.

Anyone else run into this?
Ideas on how to side-step this?

 

[sonic8]

Can you provide a minimal sample db to reproduce the issue?

PS: You also should have mentioned that you asked about the same problem before.

 

[Papa_Bear1]

Can you provide a minimal sample db to reproduce the issue?

PS: You also should have mentioned that you asked about the same problem before.

Wow - I had done a search but not within this site yet --- and so I didn't happen up on my old post! Yikes... And it was the EXACT same problem... Ugh... Sorry about that...

I'd like to supply code, but I'd have to find time to create that, and I may just give up ---- because ----

One extra tidbit, while I'm here ---
While in debug mode and the error is still occurring, I tried to do a manual import using that same spec. It coughed up the error talking about the Wizard not being installed. Also something that is obviously not true since it ran successfully 3x in that loop just seconds before.

This sure feels like an obscure bug that is possibly/somehow tied to how my MS Office/machine is configured (not up to me...). So, the likelihood of MS either fixing the bug, or someone in IT actually solving it is probably mathematically zero. This likely means I'll just have to abandon this approach - or so it seems to me.

 

[Gasman]

Well, first thing to try is another computer?
Are you sure the spec name is not being amended somehow, or is it harcoded?

 

[The_Doc_Man]

In this loop, by any chance do you have a section in a subroutine for which you have an ON ERROR RESUME NEXT ?? Do you have a section in a sub for which you do a DoCmd.SetWarnings FALSE? (Or 0?)

 

[DHookom]

I would create a query with this SQL to show all your import/export specs

SELECT MSysIMEXSpecs.SpecName, MSysIMEXColumns.FieldName,
MSysIMEXColumns.DataType, MSysIMEXColumns.IndexType,
MSysIMEXColumns.Start, MSysIMEXColumns.Width
FROM MSysIMEXColumns INNER JOIN MSysIMEXSpecs
  ON MSysIMEXColumns.SpecID = MSysIMEXSpecs.SpecID;

 

[CJ_London]

I'd like to supply code, but I'd have to find time to create that,

You didn’t last time either. So you are happy for us to spend time on your behalf guessing what the issue is?

Only suggestion I can make is there is an issue with the file you are trying to import- perhaps too big or corrupt? Have you tried skipping that file?

I’m not sure your tidbit is a valid test if the code is still running even if paused due to an error

 

[gemma-the-husky]

What line of code displays the error? Can you not display the spec that it's trying to use to make sure you understand the error?