Library databases in Access 2000
I would not recommend that sort of thing too often, lest you
run into the very corruption issues they were trying to
avoid....
--
MichKa
-------------------------------------
don't send questions by e-mail unless
you're paying for it. (TANSTAAFL!) :-)
random junk of dubious value and
replica error and problem fixing at:
http://www.trigeminal.com
Quote:
> Thanks for your response. I was disheartened when I read
it, but I
> generally don't give up. I found a rather kludgey work
around. It's not
> elegant, but it works.
> By opening the project explorer, you can drag and drop the
module from the
> library into your current database, make the changes and
save it. Then
> remove the original module from the library (yes, that
works - can delete
> but not add or change #!#!) and drag the module from the
app database to the
> library.
> Michael (michka) Kaplan
Quote:
> > No, there is no way to do this. Library dbs cannot have
> > changes saved to them, period. This is a feature of
Access
> > 2000 and its save model changes (an afterthought
designed to
> > get rid of a few of the crash bugs).
> > Don't like it? You're not alone. I know a few people who
> > moved back to 97 for this change alone. My list is a lot
> > longer, and this is only 18th on my list, but its there.
> > --
> > MichKa
> > -------------------------------------
> > don't send questions by e-mail unless
> > you're paying for it. (TANSTAAFL!) :-)
> > random junk of dubious value and
> > replica error and problem fixing at:
> > http://www.trigeminal.com
> > > I commonly use a library database attached to all of
my
> > application
> > > databases. This has worked well in all prior versions
of
> > Access. The
> > > problem is: the library database is continually
evolving.
> > I used to be able
> > > to open a routine in the library and edit it (while
> > debugging both the app &
> > > the library); I could save the library.
> > > With Access 2000, I can view the library & even make
> > changes during testing,
> > > but I can not save the changes. I've tried opening a
> > separate Access
> > > instance to load the library, but I then can not save
> > anything due to
> > > sharing problems.
> > > So, I tried to export the changed module after I was
> > finished, then open the
> > > library, delete the original module, then import the
.bas
> > file. This
> > > worked, with a lot of effort. But, now the module
does
> > not show in the
> > > Access DB Window; however it does show in the Project
> > Explorer window.
> > > Pretty wierd!
> > > Hey Microsoft, is there a way to enable saving changes
to
> > a library database
> > > while working in the application mdb?
> > > HELP!
