Geert, with respect to the Code Generation features of EA, in .NET, code generation is almost always done for a Visual Studio "project", which usually ends up being the Namespace of the underlying classes that are generated (a simplification, but a useful one). If I am just modelling in EA, I don't need a project name, but if I want to generate .NET code from the model, I want to be able to put a default namespace in the generated classes. I reasoned that the best way to do this (without, of course, interrupting the user with a dialog that actually ASKS for the namespace) is to use the project name/file name of the .EAP project. This is easy if the .EAP is just a file (Access), but gets difficult when you go to storing your EA project in a DBMS. I hope this explains what I need this for a little better.
KP, that is good to know about the DBType, but then I still have to parse the myriad connection strings that can be used to connect to the different DBs to get the "Project Name".
Geert may be on to something when he mentions the root package name in the model. Perhaps it is better to just get the namespace from the package itself...