Yeah, it's got an API.
-
We have a process at work that interfaces with some third-party software through that software's "API" (and I am using that term loosely). The nature of the interaction is we send LOTS of data to the software and it does some transformations, sorting and accuracy checking, then returns the final list. Sometimes this software encounters some errors. Ok, you would think the API would return an error back to the calling program. Nope! Instead it pops up a Windows Error Message dialog box. This process is completely automated, running as its own user on the server. Nobody is ever alerted that there's a problem. We had to code in a timer in the calling app and if we don't get the output back within 30 minutes we abort the process. Yesterday this scenario occurred, so today I'm sitting here running this 6-hour long process manually under my user account babysitting it looking for the error popup so I can click "ok". There's no reason for the popup, if the software encounters an error in the data, it removes that data entry from the set. Why does it need to popup a box telling the user it found an error?
Don't blame me. I voted for Chuck Norris.
-
We have a process at work that interfaces with some third-party software through that software's "API" (and I am using that term loosely). The nature of the interaction is we send LOTS of data to the software and it does some transformations, sorting and accuracy checking, then returns the final list. Sometimes this software encounters some errors. Ok, you would think the API would return an error back to the calling program. Nope! Instead it pops up a Windows Error Message dialog box. This process is completely automated, running as its own user on the server. Nobody is ever alerted that there's a problem. We had to code in a timer in the calling app and if we don't get the output back within 30 minutes we abort the process. Yesterday this scenario occurred, so today I'm sitting here running this 6-hour long process manually under my user account babysitting it looking for the error popup so I can click "ok". There's no reason for the popup, if the software encounters an error in the data, it removes that data entry from the set. Why does it need to popup a box telling the user it found an error?
Don't blame me. I voted for Chuck Norris.
-
Yes I use something similar too from a windows service. :)
-
It might, thanks. The ultimate solution is to switch to a better solution. There have already been rumors about switching to a different software package for this. Normally during the week this isn't a problem as our app sends off an email as soon as something fishy has happened. Yesterday was Saturday though and I wasn't in the office to get the email.
Don't blame me. I voted for Chuck Norris.
-
We have a process at work that interfaces with some third-party software through that software's "API" (and I am using that term loosely). The nature of the interaction is we send LOTS of data to the software and it does some transformations, sorting and accuracy checking, then returns the final list. Sometimes this software encounters some errors. Ok, you would think the API would return an error back to the calling program. Nope! Instead it pops up a Windows Error Message dialog box. This process is completely automated, running as its own user on the server. Nobody is ever alerted that there's a problem. We had to code in a timer in the calling app and if we don't get the output back within 30 minutes we abort the process. Yesterday this scenario occurred, so today I'm sitting here running this 6-hour long process manually under my user account babysitting it looking for the error popup so I can click "ok". There's no reason for the popup, if the software encounters an error in the data, it removes that data entry from the set. Why does it need to popup a box telling the user it found an error?
Don't blame me. I voted for Chuck Norris.
-
Appaling Program Interface?
Join the cool kids - Come fold with us[^]
-
We have a process at work that interfaces with some third-party software through that software's "API" (and I am using that term loosely). The nature of the interaction is we send LOTS of data to the software and it does some transformations, sorting and accuracy checking, then returns the final list. Sometimes this software encounters some errors. Ok, you would think the API would return an error back to the calling program. Nope! Instead it pops up a Windows Error Message dialog box. This process is completely automated, running as its own user on the server. Nobody is ever alerted that there's a problem. We had to code in a timer in the calling app and if we don't get the output back within 30 minutes we abort the process. Yesterday this scenario occurred, so today I'm sitting here running this 6-hour long process manually under my user account babysitting it looking for the error popup so I can click "ok". There's no reason for the popup, if the software encounters an error in the data, it removes that data entry from the set. Why does it need to popup a box telling the user it found an error?
Don't blame me. I voted for Chuck Norris.
I used to work with something like that, it was called VB6. :-D
-
We have a process at work that interfaces with some third-party software through that software's "API" (and I am using that term loosely). The nature of the interaction is we send LOTS of data to the software and it does some transformations, sorting and accuracy checking, then returns the final list. Sometimes this software encounters some errors. Ok, you would think the API would return an error back to the calling program. Nope! Instead it pops up a Windows Error Message dialog box. This process is completely automated, running as its own user on the server. Nobody is ever alerted that there's a problem. We had to code in a timer in the calling app and if we don't get the output back within 30 minutes we abort the process. Yesterday this scenario occurred, so today I'm sitting here running this 6-hour long process manually under my user account babysitting it looking for the error popup so I can click "ok". There's no reason for the popup, if the software encounters an error in the data, it removes that data entry from the set. Why does it need to popup a box telling the user it found an error?
Don't blame me. I voted for Chuck Norris.
It's not the only one, I've had to work with shit 3rd party software like that as well. You can probably use FindWindow etc functions to look for the window handle read the text and then programatically click the right buttons etc if it's always the same kind of thing.