A 4D database that has been making successful ODBC calls to an external database, such as MySQL, PostgreSQL MS SQL, etc. may suddenly experience an error when making an ODBC query like the one shown below.



A recent Microsoft system update, or patch, has lowered the default maximum size of system resources that an applicaiton can request. The cause of this error most likely exists in the memory settings for the 4D database.

What this error dialog, and other similar dialogs from the OS, means is that the amount of memory being requested by 4D exceed what the OS is willing tp provide. In this case the ODBC driver is acting as a proxy for 4D, but the origin of the memory request is from 4D.

The amount of memory that 4D has access to is limited by the OS, not 4D, since it is the OS that handles memory management. The solution at this point is to investigate how much memory 4D is demaning for its cache or stack and adjust accordingly.

There are numerous assets on 4D Knowledgebase that provide guidance on setting the 4D cache and stack sizes.