>That's what I've been doing as well, but I was curious whether the database opens a second connection when the first view is opened.

The framework opens the views using Connstring {nHandle} clause. Haven't really checked whether it uses a different connection without it - probably does, but I wouldn't know offhand. You may have one of each open and watch in the profiler on your SQL server whether they were using the same connection.

>Also, does that connection 'time out' and the handle become invalid if it is not used for a while?

Not that I've noticed, but that doesn't mean it doesn't do that - I've always had some "set it and forget it" kind of framework at hand, and in the current framework there's a handle_access method which rechecks the connection and reestablishes it if broken. The break doesn't necessarily have to be caused by a timeout - it can caused by anything else, like cable break, paranoid security behaviors, server down or magic smoke emanating from your NIC ;).

>And, since the DBC is included in the project, is there a way to update the connection string in the DBC when it is opened?

Use Connstring [handle] instead. I know it's a confusing syntax, the clause says string and you supply the actual handle, but it works. So the string and the connection in the DBC are needed only during development; at runtime you need just a handle.