Re: Blat Error Handling

I have used error detection with Blat in a batch file. Here is an 
example from a batch file. This code is just after Blat is called.

---------------
:: If there is an error, don't delete the alert file
if not errorlevel 0 goto Other
del C:\Scripts\Alert.txt

:Other
----------------

I set this up for pretty much the same reasons as you're talking about, 
handling not being able to send because the network is down.

On 11/26/17 6:23 AM, [email protected] [blat] wrote:
> Goedenavond Luko!
>
>
> Intergrating blat.dll into the POS is currently not an option, as we
> lack the resources. Lots of other important Development is going on, and
> we hope to resolve the need for sending automatized results using blat.exe.
> The Batch Files are almost completely developed, they encompass all
> currently necessary cases, and we also compiled an installer for it
> (Using Innosetup), so distributing the package to our customers isnt a
> problem.
> The only thing we are really stuck at this very moment is the Error
> handling in case of no available Internet. The Errors we receive in this
> case are not recognized by the documented Blat Errors, they seem to not
> return an Errorlevel which we can hanlde. As a result our batch would
> now inevitably delete unsent reports.
> Is this a bug in blat? Or am I missing a documentation?
> Can this be resolved using Powershell? Different Errorcodes? I have
> learnt a fw things in Bath languge now in the last few months, but have
> no prior experience in Powershell
>
>
>