...working.
I'm going to do my best to explain it carefully. It has been a LONG time since I dug this deep into what I created a long time ago. I know the names for tables, macros, etc. are not professional... but it has worked for a loooooong time, and I can certainly fix that, but I *really* need to get this back up and running and retire the old machine.
The preface is that I have a db that imports data from two flatfiles via ftp these files are created in "batches" whereas data is collected on them, then once a day (sometimes more, sometimes less) the data is imported in Access, the two files are deleted, and two new files (same names) are created upon the first new entry of data... and repeat, repeat, repeat. There's more to it, but for purposes of this problem... I *think* that is the salient information.
Here we go!
I have a Form. On this form there is an "OnClick" that takes you to a Macro called "Download OL"
"Download OL" does a RunApp that runs a file on c:\MyPlace\Import.bat
The object of this file, Import.bat, is multi-faceted.
First: It renames the previously imported flat files and changes their extension to .bak (there are two flat files that the db uses) (this change is made on the PC side on the c: drive)
Second: It takes the new (not yet imported flat files) and changes them from .txt to .txt-locked so that there is no interference if new data is being submitted at the same time. (this change is made on the FTP side via FTP -s:filename.txt domain.com
The filename.txt file looks like this:
username
password
passive
cd /public_html/dir/dirnext/
ascii
prompt
rename 123.txt 123.txt-locked
rename asd.txt asd.txt-locked
mget 123.txt-locked
mget asd.txt-locked
bye
AND HERE IS THE PROBLEM...
It stalls/stops working at the mget command. It never downloads the 123.txt-locked (or the asd.txt-locked) files and puts them in the dir on the PC side.
That's it! That's all I need to know. LOL. How can I get the mget back to working? The funny part is that it works perfectly fine on the current Windows 10 machine, but refuses to work on the new one.
Sorry for such a long post for what must seem like a simple problem to you folks, but tracing it like this was the only way I could get there from here.