Edgar,

And when we talk about managed connections there is no need to have a meaningful connection ID name anymore. Most people did this (need to do that) in the time the connection ID name was stored in the <driver>.int file. As an example I tend to always use ID1 as the connection ID in the dfconnid.ini file. The only case where it a meaningful name makes sense is when your application uses two or more different databases at the same time; the connection ID name then might make it easier to directly know the name of the database.

Compare this with the name of the workspace (.ws) file. Prior to DataFlex 11 this name needed to be unique (in the early days stored in the registry and later in a workspaces ini file) but since "modern" times the default is "just" config.ws. No need for <Company>.<Application>.ws or something like that.