--- In IBObjects@y..., lester@l... wrote:
> As they are in IBO4 is not really OK. As they were in IBO3.6 worked.

> There are two separate problems which a lot of people will never
see.

Can you please explain to me the differences? I never used IBO 4 and
I don't know what are you talking about.

>
> 1/ Some systems just do not need passwords, they are a hindrence
and so get
> switched off. This can be done in program fine so no changes are
needed.
>

All programs that use ib need a password. If a specific app in a
specific machine do not need one, this could no be done the way Jason
suggest: using the environment. If security it's not a problem, there
is no problem to put it on the environment.

> 2/ Some of us develop accross more than one machine - and it is a
pain in
> IBO4 to have to reset the password in the development environment
just
> because you are trying to debug on a slave machine. If you only
ever use one
> machine you will never see this problem.
>

Ops, I really do not have this problem. I think your problem it's not
developing in one machine, but with different IB servers, rigth? In
your work, you have different passwords for different IB servers.
Could we use this as a rule for people who program in different
machines? I don't know, and we are going to get some opinions from
other developers that work in different machines / different IB
Servers.

HELP WANTED ON THIS!

> We do need a change, the question is should it be the 'bells and
whistles'
> version. Now that I have been caught twice because I have had to
rebuild and
> reinstall a development machine, I am thinking that Option 2 may
have even
> more going for it.
>

Maybe I change my opinion after someone explain to me the differences
using the password between IBO 3 / 4.

Artur Anjos