A built 4D Client-Server application provides an efficient way to deploy a 4D database application to multiple users. The compiled application ensures source code security and gives developers control over the user experience. However, a common limitation of 4D Client-Server deployment is that a 4D Remote Client cannot execute developer-written code until it successfully connects to a 4D Server.

To address this, 4D allows a built 4D Remote Client to start with a standalone database, enabling it to execute code without an initial server connection. This Technical Note explores the process of embedding a standalone 4D database within a 4D Remote Client. Additionally, it presents a sample implementation demonstrating how a 4D Remote Client can automatically connect to a primary server and failover servers.