S
Scott Burke
Hello everyone. Thank you for your time and considerable understanding. I
have finial figure out what the problem was with our FTP problems!!!
When I came back to work here (10 months ago) I was asked to look into a
little problem they were having. Files that they were trying to ftp were not
getting to the customer! The FTP engine that was being used would NOT give
me any information so I decided to change the FTP engine to WININET.DLL. As
you know the Wininet.dll will give you errors 7 ways too Sunday. Keep in
mind that I only changed the FTP engine and NOT the logic the program was
using. (remember that)
The ftp logic was tying to FTP two files. The CDS orders and CDS cancel
files. They keep getting a ‘PUT’ error when the FTP engine ran. The
clearing department would call me and tell me about the error. I then
instantly (remember that) went into the code and ran my test macro. Both
files FTP perfectly!!! NO errors! I then put my situation on the board for
help.
I thank all of you for your time and ideals.
Here was the problem.
Firstly, The CDS button that tried to FTP the two (2) files and the result
was an error. Well as it turned out only one (1) file existed at that time.
That would be the CDS cancel file. The CDS orders file would not be created
until step 2 in the program. Can you say "PUT Error"?
Secondly, remember when they called me about the error. Well, they waited
until they were in step 2 and they had pressed the CDS button ,that had
created the CDS orders file , before telling me that the error happened. SO
when I ran my test FTP macro, both files actually existed. Thus the FTP
engine worked perfectly!
As I sit here I can not help but wonder how I can stop this situation from
happing again. I can only come up with one (1) solution. A quick right hook
to the jaw followed by several rapid blows to the chest and torso with a lead
pipe.
Any ideals.
Scott Burke
have finial figure out what the problem was with our FTP problems!!!
When I came back to work here (10 months ago) I was asked to look into a
little problem they were having. Files that they were trying to ftp were not
getting to the customer! The FTP engine that was being used would NOT give
me any information so I decided to change the FTP engine to WININET.DLL. As
you know the Wininet.dll will give you errors 7 ways too Sunday. Keep in
mind that I only changed the FTP engine and NOT the logic the program was
using. (remember that)
The ftp logic was tying to FTP two files. The CDS orders and CDS cancel
files. They keep getting a ‘PUT’ error when the FTP engine ran. The
clearing department would call me and tell me about the error. I then
instantly (remember that) went into the code and ran my test macro. Both
files FTP perfectly!!! NO errors! I then put my situation on the board for
help.
I thank all of you for your time and ideals.
Here was the problem.
Firstly, The CDS button that tried to FTP the two (2) files and the result
was an error. Well as it turned out only one (1) file existed at that time.
That would be the CDS cancel file. The CDS orders file would not be created
until step 2 in the program. Can you say "PUT Error"?
Secondly, remember when they called me about the error. Well, they waited
until they were in step 2 and they had pressed the CDS button ,that had
created the CDS orders file , before telling me that the error happened. SO
when I ran my test FTP macro, both files actually existed. Thus the FTP
engine worked perfectly!
As I sit here I can not help but wonder how I can stop this situation from
happing again. I can only come up with one (1) solution. A quick right hook
to the jaw followed by several rapid blows to the chest and torso with a lead
pipe.
Any ideals.
Scott Burke