DDL Script Generation

[rhoff999]

We have a utility application written in C# we use to run against generated DDL to add addtional configuration and global table changes.  It utilizes the .NET StringBuilder class.  With all previous versions of EA, the DDL script processed no problem.  Now with version 6, the StringBuilder search methods seem to get "hung up" and never return.  It is like the script contains some UNICODE character it cannot process.  Any idea why this new DDL generation would be causing this?

[«Midnight»]

I think the EA product has become fully Unicode as of version 6. There used to be two versions of each build - one Unicode and one for 8-bit characters. Now there seems only to be one, and it is Unicode. You'll have to tweak your model a bit to account for this, and the problem should go away.

Unfortunately, without knowing the specifics of the problem I cannot offer a quick fix.