I have a DB conversion app with a lightweight GUI, mainly just labels that get
updated to indicate progress. The main work (and all of the the data access) is
in a separately threaded class module in the same project. I am making heavy
use of OleDbDataAdapters and it seems to be the case that I can declare a data
adapter in the class module but if I do so there is no way to use the built-in
wizard which initializes it, thus I would have to hand-code hundreds of lines of
initialization which the wizard accomplishes with a few clicks. So I have ended
up dropping them all these adapters (dozens!) onto the GUI form and then
initializing references to them in the DB access module. This creates a
completely inappropriate dependency (to me, YMMV) between the form and the class
module.
This all just seems so perverse, since the only GUI aspect of the data adapter
is the design-time wizard itself. So am I simply missing something here? Is
there some way to declare the adapter in its appropriate location (the class
module) and still have access to its wizard? (I realize that that I can use the
form to initialize them and then copy/paste all the generated code to the other
module - but this is even more perverse, IMO.)
In case it matters, I am currently using the 1.0 framework - planning to upgrade
soon, probably to the 2003 version.
Thanks,
-rick-
