Answered by:
How to run a .bat file through MSACCESS - Was previously working for me!

Question
-
Hi All,
I have previously been running a .bat file through access which uploads a .txt file.
It was working fine until about 2 weeks ago when IT changed us to some new network drives.
now it's not working... it looks like it is working but the file isnt getting uploaded, i checked the ftp location and the file isn't there
basically that i did is
using the "RunApp" command put in U:\HPI\Runx.Bat
inside the Runx.bat
ftp -i -n -s:noetixhpiftp.txt
inside the noetixhpiftp.txt
open ADDRESS PORT user USERNAME PASSWORD
prompt off hash binary put HPI_SALES.TXT close bye
now the cmd pops up and goes away (even when i take off the close/bye command) and doesn't upload the file
when i run the .bat file manually it uploads the file fine!
please help! argh!
Mark
Wednesday, July 25, 2012 11:01 AM
Answers
-
Hi,
Thank you,
I don't know why but using the file name only worked previously.
nothing has moved other than the network drives (everything was kept with the same name etc just new physical drives with the data transfered).
however i fixed this problem by putting in the full file path of the file and it worked fine (instead of just the filename)
no idea why it worked before lol but this is sorted now.
Mark
- Proposed as answer by Dummy yoyo Friday, July 27, 2012 8:17 AM
- Marked as answer by TropicoLa Friday, July 27, 2012 8:18 AM
Friday, July 27, 2012 8:13 AM
All replies
-
Hi Mark,
Welcome to the MSDN forum!
>> when IT changed us to some new network drives.
What has been changed now? The location of the bat file or the noetixhpiftp.txt file?
Is the bat file in the local drive or a mapped network location?
Is it OK to run the bat file from Command line?
Thanks.
Yoyo Jiang[MSFT]
MSDN Community Support | Feedback to us
Friday, July 27, 2012 7:02 AM -
Hi,
Thank you,
I don't know why but using the file name only worked previously.
nothing has moved other than the network drives (everything was kept with the same name etc just new physical drives with the data transfered).
however i fixed this problem by putting in the full file path of the file and it worked fine (instead of just the filename)
no idea why it worked before lol but this is sorted now.
Mark
- Proposed as answer by Dummy yoyo Friday, July 27, 2012 8:17 AM
- Marked as answer by TropicoLa Friday, July 27, 2012 8:18 AM
Friday, July 27, 2012 8:13 AM -
Thanks for your sharing and have a nice day.
Yoyo Jiang[MSFT]
MSDN Community Support | Feedback to us
Friday, July 27, 2012 8:25 AM