Read proxy Server Info File

[NewsArchive]

Question: When the Read Proxy Server Info File returns an %_SB_ERRORCODE% =
1
does this mean:
1) The file could not be found, readm or doesn't contain the correct entries
-or-
2) It read everything but there was some internal problem that did not allow
the proxy information to actually be retrieved from the specified location?

The help system doesn't define what any of the potential problems or error
codes code mean.

Thank you,

Mike

[NewsArchive]

Mike,

The "Read Proxy Server Info File..." script function returns 1 if the proxy
server file was not accessible. Otherwise, it returns 0.

Friedrich

[NewsArchive]

By the way, there is a new "Set Proxy Server Info..." script function in
SB74 now. This function can be used to programmatically set the proxy
information through variables.

Friedrich

[NewsArchive]

I've made absolutely sure that the file specified for Read Proxy Server File
Info to read is in place.
The string is : %PROXY_INFO_FILE_DIR%\EC_PROXY_INFO.INI

I display the string using DisplayMessageBox and it shows the proper
location of the file.
I've opened the file to be sure its there.

It "Read..." script function returns a "1" every time.

The INI file contents are just dummy info for testing

[PROXY]
Server=SERVER
Port=80
User=USERNAME
Password=password


Since the error message returns "1" when the file is not accessible this
makes no sense.

Can you shed some light?

Thank you.

Mike
I am using build 7.3.3228

[NewsArchive]

Hi Mike,

Yes, I think I see what is going on. The function does not resolve the
%PROXY_INFO_FILE_DIR% variable :-( If you specify a "fixed" path then it
works fine (bug!).

Thank you for bringing this to my attention. It's fixed now and will be
available in te next maintenance build.

Friedrich

[NewsArchive]

Thanks for checking Friedrich. So glad I wasn't going crazy.

I will look forward to your maintenence build.

Mike

[NewsArchive]

Thank you for the update Friedrich.

This works perfectly now!

Mike

[NewsArchive]

> Thank you for the update Friedrich.
>
> This works perfectly now!
>

Thank YOU, Mike!!!

Friedrich