In theory, it should work regardless of whether they are in separate databases or not. In reality, it depends upon how they implemented their db classes. For example, are they using a thread resource pool? If not, any real loading will likely result in some odd behavior.
That said, I would first try to ensure it works with an integrated db. Then, once things are working smoothly, repoint vb to it's original seperate db by exporting the integrated db, and loading it into the seperate db.
By doing this, you limit potential sources for error during your trouble shooting phase. Ymmv, of course.
|