Resource access has been changed in 4D v11 SQL.

4D or System resources

4D or system resources can no longer be used. This includes custom constants in the structure resource file. For an upgraded database the RSR and 4DR file are still automatically loaded but this does not circumvent the use of 4D or System resources.

Custom Resources

The behavior did not change, however all custom resource files should be placed in a folder named “Resources” next to the structure file. Note that these resource files must be loaded manually, 4D does not automatically load them.

Note: it is recommended to stop using resource files and convert all existing resources. For example:

• STR# resources used for localization should be converted into XLIFF.
• 4DK# resources must be converted into a plug-in stub.
• Picture resources should be converted to picture files placed in the "Resources" folder.

Component Resources

Components get their own "resource space" in 4D v11 SQL. This means that each component database can use its own custom resources with no need to modify the component code to take the host database into account.