Thank you for contacting us.
We managed to reproduce the behavior you have described. Unfortunately the cause for it is a bug on our side. Please accept our apologies for the caused inconvenience and find your Telerik Points updated for reporting this new bug. We have logged it in our backlog and it will be scheduled to be fixed in the future.
Meanwhile, we can suggest you a workaround which would allow you to use full stops in the database name. The approach involves the usage of a second OpenAccessContext object
which would be instantiated with a modified connection string. This secondary OpenAccessContext object will be used only for creating the database
in case it does not already exist. I have attached a sample project illustrating the approach. In order to run the application you may need to upgrade the references
to the OpenAccess assemblies. You may also need to update the connection strings defined in the app.config files according to your setup.
I hope this helps. Should you have any more questions, do not hesitate to get back to us.
OpenAccess ORM is now Telerik Data Access
. For more information on the new names, please, check out the Telerik Product Map