Re: My ritual question for each new version of Access since 2000
- From: w_a_n_n_a_l_l_ -@xxxxxxxxxxxxxxxxxxxxxxxxxx
- Date: Wed, 31 May 2006 13:09:57 GMT
Sounds like the only option that will work is to set a reference to the MDE
in your live project, and then wait until last user is out to replace that
MDE.
I haven't seen the problem you describe of not being able to modify the MDB
just because someone is in the MDE. I can imagine the possibility that if
you put the MDB and the MDE of the library in the same directory, presumably
having the same name other than MDB and MDE, since you can only have one LDB
you could have a problem. But the real problem there is putting both MDB
and MDE in the same production directory. One or the other, but not both,
ever.
And in development, since you have to be out of the main project to release
the MDE anyway, there shouldn't be a problem with modifying the MDB and then
creating the MDE.
.
- Follow-Ups:
- Re: My ritual question for each new version of Access since 2000
- From: David W. Fenton
- Re: My ritual question for each new version of Access since 2000
- References:
- My ritual question for each new version of Access since 2000
- From: Mathieu Trentesaux
- Re: My ritual question for each new version of Access since 2000
- From: david epsom dot com dot au
- My ritual question for each new version of Access since 2000
- Prev by Date: Re: Hide Query Output
- Next by Date: Re: Make linked table have a relative path
- Previous by thread: Re: My ritual question for each new version of Access since 2000
- Next by thread: Re: My ritual question for each new version of Access since 2000
- Index(es):
Relevant Pages
|