I have noticed that there are quite a few configuration variables that validate and are defined in the pre-processor and the debugger but are not defined after the threshold at application runtime.

That makes the configuration variable broken or not working or not inherited at runtime of MicroStation.

Another issue is some variables require encapsulation and enclosure in inverted commas to wrap configuration variable values to ensure that all syntax, including spaces between words, is captured. This is particular the case for file directory paths where they are hard coded.

Also, I have noticed three different instances where custom values are assigned to configuration variables:

Assigning a custom configuration value to an MS application defined variable, returns an application fault,
Assigning long file pathname [with spaces] to an application defined configuration variable returns an application fault, whilst assigning the long file pathname to a custom configuration variable and then assigning the custom variable to the application variable does not return the same fault.

Essentially there are two issues here but a parity check of identical conditions for all configuration variables parsed by the preprocessor before the threshold to runtime might solve a lot of these inherent and piecemeal bugs and faults.