Tech Tip: More to Know About Using Packproject=false, Specifically in Client/Server Deployment
PRODUCT: 4D | VERSION: 21 | PLATFORM: Mac & Win
Published On: March 31, 2026
The PackProject key is defined in the buildApp.4DSettings file, under:
/Preferences4D/BuildApp/PackProject
This setting controls how the built application is generated. By default, the application is created as a read-only .4dz packaged file. When this setting is set to False, the application is built as a standard Project folder containing only compiled code.
In a Client/Server environment, setting PackProject=False restricts modifications to the local data model to server-side code only.
As a result, commands such as ARRAY TO LIST executed from a 4D Remote client will have no effect on the server. Any 4D commands that modify the application definition—such as those involving lists—must be executed on the server.
/Preferences4D/BuildApp/PackProject
This setting controls how the built application is generated. By default, the application is created as a read-only .4dz packaged file. When this setting is set to False, the application is built as a standard Project folder containing only compiled code.
In a Client/Server environment, setting PackProject=False restricts modifications to the local data model to server-side code only.
As a result, commands such as ARRAY TO LIST executed from a 4D Remote client will have no effect on the server. Any 4D commands that modify the application definition—such as those involving lists—must be executed on the server.