For starters, the simplest way is to hardcode encoded password (encode using some simple algorithm that is a part of your application. Then, when the app runs, decode it and build connection string on the fly. Basically, this is quite a common problem, many compilers treat literal constansts in the same way (VB, etc.). If you want to be more sophisticated, keep encrypted password in registry and embed decryption code into your app. As far as I know, Delphi can consume COM objects and it seems to me that Microsoft has some COM wrappers for their Win32 CryptoAPI library. Personally, I just use this library with Visual C++. Quite simple. I am not familiar with Delphi, but if you can call Win32 C functions from within Delphi code, this is the way to go (my assamption you are developing on Microsoft platform). Good luck.

To Valdemar...

Nope, it is not DOS encoding, it is password XORed with something. And basically, this is how all symmetric encryption algorithms work (plus permutation). Generally speaking you are right - executable file is not the right place to keep password. Even more, a PC itself is not the right place either. If you anticipate that your code may be attacked by a professional crypto-analyst, get yourself a smart id card or something else of this kind. National Security Agency (something our late FAPSI was similar to) never implements encryption algorithms as pure software solutions - always as tamper-resistant microchips. But we are not talking here about NSA or FAPSI, aren't we? For common end-users keeping encrypted connection string in registry is enough. What are you protecting, anyways? Viably important state secrets? Hardly. And for corporate junk this will do.

PS: Sorry for using English, I am on a corporate comp, not allowed to install another locale and hate to write Russian with Latin fonts. Such a mess comes out.