Thanks Salad. That did the trick.
Larry the DB is re-created with new products from an external source.
To be honest I really don't wanna get into this area - can of worms,
probably doesn't need to.
Out of interest how does one share vba code around, i.e. say I have a
couple of BAS modules with lots of useful routines. Linking seems to
work only with tables? Import just SEEMS to copy the bas module over
What I'm trying to achieve here is in case of code fix, I don't have
to change every DB that references it. But change the one that all
others "link to".
Short of compiling it into a VB dll and referencing it in Access,
which still wouldn't be ideal, but would probably still need a bas
module as a wrapper to instaniate and wrapp teh calls to the dll.
Larry Linson wrote:
"Yitzak" <te*********@yahoo.co.ukwrote
I've got a mdb that is recreated monthly/weekly.
If you'd explain what you have, what you are trying to accomplish, and why
you felt it necessary to re-create weekly and/or monthly a database into
which you have to copy a module, perhaps someone can offer you useful
suggestions. My comment would be, perhaps you have an exception, but there
is almost never a compelling reason to re-create a similar database on a
periodic basis.
I've written a bas module with lots of functions
in it so that they can be used in queries.
>
What is an easy way to import the bas module
into the newly created mdb. I've exported it as
a text file.
If there is some compelling reason why you can't use Salad's suggestion of
importing the module directly from the database where it resides, then you
can open a new module in the new database, highlight, copy, and paste the
module code.
Larry Linson
Microsoft Access MVP