Bad practice? Stoopid to do that?

I have been working on a project, and a possible solution to a problem was to create some views that contain tables from more than one database (I had a LoanDB and an ArchiveLoanDB - tables in ArchiveLoanDB had records that were moved from LoanDB; these records pointed to some definition tables in LoanDB). This was an "easy" way to reuse some code that operated on LoanDB (producing statements, displaying loan info). I had a view, w/the same name, in each DB - that used definition tables from LoanDB.

It seemed to work (Stonefield didn't like it, though). I've decided to go another, simpler, way, for this specific problem, but thought I'd run the idea past the experts, for future reference.

Any comments/input?

TIA, J

PS nice view of the 5:00 AM lunar eclipse this morning...although the clouds moved in quickly, and now it's raining ;-(