Search results

  1. Papa_Bear1

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

    Interesting... I'm experimenting with PowerShell at the moment. I've barely done anything with it, so my first attempts, although working with small files, are abysmal with the big files - just too slow. It seems to be very difficult to just pull data into anything other than a single...
  2. Papa_Bear1

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

    The files contain X-Y-Z data from a geotif file, space-delimited with Longitude Latitude Elevation data, and I'm only retrieving the elevation data, and by placing the data into an array in the proper position, I need not store the Lat/Lon. Parsing that 3rd column out was another little...
  3. Papa_Bear1

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

    I see - I wasn't really aware of when/where the cleanup occurred for the recordset, and certainly was not aware of the multiple pieces to it internally. There is always more going on under the hood than I'm imagining (especially in THIS world... :) ) As far as the rows/columns thing - in this...
  4. Papa_Bear1

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

    Well - in this particular instance - I'm having to process a very large amount of information, and every time I try to use tables - it either gets too big for Access to handle, or gets too slow. I generally err on the side of storing data in tables (probably to a fault actually...), but in this...
  5. Papa_Bear1

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

    OK - so @The_Doc_Man is spot on... again... While experimenting with the file order (per @DHookom), I found that if I simply repeated ONLY the TransferText command for different files, it was fine. It progressed beyond the 3rd file etc. But when I included defining my recordset after each...
  6. Papa_Bear1

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

    Good idea. I do think I have a handle on what is happening where and when - so I've not tried to include any feedback like this just yet. (I've found this kind of feedback to be absolutely VITAL when doing recursion - including how many 'layers' in I am etc. - that's for sure!!)
  7. Papa_Bear1

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

    That's a great troubleshooting idea. In my current context, the order is rather controlled (walking an array of files that organized positionally, so I'd have to throw a monkey wrench into that to test this idea. If/when I can do that - I'll follow up.
  8. Papa_Bear1

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

    Good ideas... I did initially put a breakpoint on the TransferText command, as you might expect, but I did not yet try omitting some of the other steps - (like reading in the data etc.), which I'll try next. The only variation in what happens, though, is whether I skip doing anything with the...
  9. Papa_Bear1

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

    OK - tried this on a non-corporate-managed computer - and it does the same thing. I admit I'm quite surprised. Either the other computer has something similarly configured - or this is an actual bug of some kind (whether my code or Access). If I can find time, I'll try to whip up a simple DB...
  10. Papa_Bear1

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

    It is the TransferText command. I can indeed display the spec - in the system table, at any time. It exists before, during, and after the code runs.
  11. Papa_Bear1

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

    I understand the general principle of supplying code - but in this case, I just can't see how that matters much. I did describe what I'm doing - using TransferText, with an import spec, inside a loop, that works three times in a loop and then suddenly doesn't. Interesting point on the file size...
  12. Papa_Bear1

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

    I did look at the MSysIMEXSpecs, and it is there. In fact, if I were to restart the system and run it again - it seems it gets through three iterations - using that spec successfully, and then fails. So, it very likely isn't about the spec existing or being referenced properly etc.
  13. Papa_Bear1

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

    In this case - no - I don't have any Resume Next stuff happening, and also no SetWarnings False either (as far as I know... ;-)
  14. Papa_Bear1

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

    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...
  15. Papa_Bear1

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

    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...
  16. Papa_Bear1

    Solved A Really Simple Question

    Just trying to close the loop on some of the comments... I think I updated my comment after your comment --- as I did not have them open at the same time. Indeed that would be a little bit crazy -- ha. I think the issue I've had is probably changing data on the form that is open - perhaps...
  17. Papa_Bear1

    Solved A Really Simple Question

    Well - I would say that the form I'm working IS the one where the user chooses whether to perform the maintenance or not. It is true that I could probably just put up a YesNo MsgBox, asking for confirmation - but - I wanted to show them the path to the file they recently imported *while* asking...
  18. Papa_Bear1

    Solved A Really Simple Question

    I think I'm seeing the pros/cons on this. I've really only ever had occasion to use bound forms. I've had occasions to use unbound controls. This just happened to present itself - due to its simplicity - as a case where I *could* choose to make the form unbound, and was just wondering if there...
Back
Top Bottom