G
George
Is it possible (or advisable) to initiate a process that
lives in one mdb from within another mdb?
For example:
Suppose I have a process that adds vendors from an Access
worktable into a series of SQLServer tables.
The process that does that lives in AddVendors.mdb.
I have several other mdb's that need to add vendors; one
that handles Vouchers (Vouchers.mdb), and another that
handles Purchase Orders (POs.mdb).
I can copy the code (tables, queries, macros, etc.) for
adding vendors into Vouchers.mdb, and POs.mdb, but then I
have two places to maintain it. I'd rather create a link
to the vendor worktable from both Vouchers.mdb, and
POs.mdb; those applications would feed the worktable that
lives in AddVendors.mdb. Can I kick-off the process in
AddVendors.mdb that takes care of the Black-box activities
of adding vendors?
If so, I have a series of applications for this sort of
thing.
Thank you for your time.
George
lives in one mdb from within another mdb?
For example:
Suppose I have a process that adds vendors from an Access
worktable into a series of SQLServer tables.
The process that does that lives in AddVendors.mdb.
I have several other mdb's that need to add vendors; one
that handles Vouchers (Vouchers.mdb), and another that
handles Purchase Orders (POs.mdb).
I can copy the code (tables, queries, macros, etc.) for
adding vendors into Vouchers.mdb, and POs.mdb, but then I
have two places to maintain it. I'd rather create a link
to the vendor worktable from both Vouchers.mdb, and
POs.mdb; those applications would feed the worktable that
lives in AddVendors.mdb. Can I kick-off the process in
AddVendors.mdb that takes care of the Black-box activities
of adding vendors?
If so, I have a series of applications for this sort of
thing.
Thank you for your time.
George