From: AndrewDB on
Hi All. I need to send a "patch" to a remote user to replace a form in an
Access 2007 application. The code behind the forms of that database has been
locked with a password. In order to copy the new form into the place of the
previous one I first need to unlock the code, copy the form and then relock
the code. Everything is quite simple except I cannot get the code to unlock
from the "patch" application. The password is known to me. Any pointers will
be appreciated.
--
Kepior Senso Fumor
From: Tom van Stiphout on
On Wed, 10 Mar 2010 19:45:01 -0800, AndrewDB
<AndrewDB(a)discussions.microsoft.com> wrote:

Why are you not sending the user a completely new front-end?

-Tom.
Microsoft Access MVP


>Hi All. I need to send a "patch" to a remote user to replace a form in an
>Access 2007 application. The code behind the forms of that database has been
>locked with a password. In order to copy the new form into the place of the
>previous one I first need to unlock the code, copy the form and then relock
>the code. Everything is quite simple except I cannot get the code to unlock
>from the "patch" application. The password is known to me. Any pointers will
>be appreciated.
From: Jerry Whittle on
Hi Tom,

That was a retorical question, wasn't it? I bet that we are both thinking
the answer is "not split".
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


"Tom van Stiphout" wrote:

> On Wed, 10 Mar 2010 19:45:01 -0800, AndrewDB
> <AndrewDB(a)discussions.microsoft.com> wrote:
>
> Why are you not sending the user a completely new front-end?
>
> -Tom.
> Microsoft Access MVP
>
>
> >Hi All. I need to send a "patch" to a remote user to replace a form in an
> >Access 2007 application. The code behind the forms of that database has been
> >locked with a password. In order to copy the new form into the place of the
> >previous one I first need to unlock the code, copy the form and then relock
> >the code. Everything is quite simple except I cannot get the code to unlock
> >from the "patch" application. The password is known to me. Any pointers will
> >be appreciated.
> .
>
From: Tom van Stiphout on
On Thu, 11 Mar 2010 10:16:10 -0800, Jerry Whittle
<JerryWhittle(a)discussions.microsoft.com> wrote:

Yep. So that others may learn.

In our company when we get a new client with an unsplit db, we don't
work on their issues, but first split the db and deploy it again.
Then we work on a new FE. The OP's problems just do not happen.

-Tom.
Microsoft Access MVP


>Hi Tom,
>
>That was a retorical question, wasn't it? I bet that we are both thinking
>the answer is "not split".
From: AndrewDB on
Hi Tom. Thanks for your reply. Your guess is incorrect - the db is split but
the front end is 160Mb and cannot be sent by mail. The user is in a different
country quite far from me. The change consists of 4 lines of code that need
to be replaced. The code module is locked from viewing and I want to try and
avoid giving the user the rights to fiddle with the code. Hence my question.
How do I unlock a code module from an outside application?
--
Kepior Senso Fumor


"Tom van Stiphout" wrote:

> On Thu, 11 Mar 2010 10:16:10 -0800, Jerry Whittle
> <JerryWhittle(a)discussions.microsoft.com> wrote:
>
> Yep. So that others may learn.
>
> In our company when we get a new client with an unsplit db, we don't
> work on their issues, but first split the db and deploy it again.
> Then we work on a new FE. The OP's problems just do not happen.
>
> -Tom.
> Microsoft Access MVP
>
>
> >Hi Tom,
> >
> >That was a retorical question, wasn't it? I bet that we are both thinking
> >the answer is "not split".
> .
>