VistaDB Build 43, EntitySpaces 2007 Beta 1.1024.0

 They seem to play together, and I can run a template for my database.

But -- encrypt the database with a password and add the password to the MyGeneration connection string, and "Test Connection" replies "Successful Connection", but the MyMeta browser is empty, and when I try to run a template (same as before - dOOdads C# Concrete Class), I get errors:

Error 116 (Provider v. 3.2.1.43): Invalid password. Cannot access database:  F:\RetinaCheckDB\testme.vdb3
Error 103 (Provider v. 3.2.1.43): Cannot activate data storage header:  F:\RetinaCheckDB\testme.vdb3
Error 101 (Provider v. 3.2.1.43): Cannot open data storage or file:  F:\RetinaCheckDB\testme.vdb3
Error 117 (Provider v. 3.2.1.43): Cannot open database:  F:\RetinaCheckDB\testme.vdb3

I'm new to EntitySpaces, so this could easily be something I'm doing wrong.  Could someone please confirm that the latest beta works with an encrypted VistaDB database or suggest how I could go about solving this?

 Thanks,

Dan

p.s.  In case this is the problem, here is my connection string: Data Source=c:\test\testme.vdb3;Password=testpass;OpenMode=NonexclusiveReadOnly

Hi,

In the past I already tried to generate classes on an encrypted database and found it didn't really work ...   the easiest and most obvious solution I've found is to unset the password during development and only set it (encrypt DB) when going to production. I know it might sound like a pain but it isn't. 

Thank you for your response.  I'll do as you suggest, and that should be fine for my needs.  Because I am new to EntitySpaces and MyGeneration, I thought I might be missing something obvious.  Thanks for confirming that this is just the way it is.

Dan 

EntitySpaces works fine with password protected VistaDB databases. For some reason, MyGeneration cannot read the schema metadata it needs from password protected VistaDB files. As ElPipo suggests, for our tests against a password protected VistaDB file, we remove the password, generate from MyGeneration, add back the password, and run our tests.