protecting VBA codes

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Alex Ng

    #1

    protecting VBA codes

    Hi,

    How do I encrypt the VBA codes in forms/reports/modules for distribution?

    Thanx
    Alex


  • Trevor Best

    #2
    Re: protecting VBA codes

    On Sat, 27 Sep 2003 22:19:45 +1200 in comp.databases. ms-access, "Alex
    Ng" <aucklandu101@h otmail.com> wrote:
    [color=blue]
    >Hi,
    >
    >How do I encrypt the VBA codes in forms/reports/modules for distribution?[/color]

    There is a password protection for them otherwise just create an MDE
    for distribution (keeping the MDB for development).

    --
    A)bort, R)etry, I)nfluence with large hammer.

    Comment

    • Alex Ng

      #3
      Re: protecting VBA codes

      thanx, that was simple enough.

      "Trevor Best" <bouncer@localh ost> wrote in message
      news:us0bnvsi5s 63fb6gb7oe85lis l84ml59gh@4ax.c om...[color=blue]
      > On Sat, 27 Sep 2003 22:19:45 +1200 in comp.databases. ms-access, "Alex
      > Ng" <aucklandu101@h otmail.com> wrote:
      >[color=green]
      > >Hi,
      > >
      > >How do I encrypt the VBA codes in forms/reports/modules for distribution?[/color]
      >
      > There is a password protection for them otherwise just create an MDE
      > for distribution (keeping the MDB for development).
      >
      > --
      > A)bort, R)etry, I)nfluence with large hammer.[/color]


      Comment

      • Larry  Linson

        #4
        Re: protecting VBA codes

        But, you should be aware that the concensus opinion of experienced Access
        developers is that they can recreate a database application in very little
        time if they can observe the user interface in operation. That is a
        concensus opinion with which I am in agreement, just for the record.

        That's not to say you shouldn't use MDE, but only that you shouldn't believe
        it will _really_ "protect you from having your application stolen".

        Larry Linson
        Microsoft Access MVP

        "Alex Ng" <aucklandu101@h otmail.com> wrote in message
        news:bl42hn$t56 $1@lust.ihug.co .nz...[color=blue]
        > thanx, that was simple enough.
        >
        > "Trevor Best" <bouncer@localh ost> wrote in message
        > news:us0bnvsi5s 63fb6gb7oe85lis l84ml59gh@4ax.c om...[color=green]
        > > On Sat, 27 Sep 2003 22:19:45 +1200 in comp.databases. ms-access, "Alex
        > > Ng" <aucklandu101@h otmail.com> wrote:
        > >[color=darkred]
        > > >Hi,
        > > >
        > > >How do I encrypt the VBA codes in forms/reports/modules for[/color][/color][/color]
        distribution?[color=blue][color=green]
        > >
        > > There is a password protection for them otherwise just create an MDE
        > > for distribution (keeping the MDB for development).
        > >
        > > --
        > > A)bort, R)etry, I)nfluence with large hammer.[/color]
        >
        >[/color]


        Comment

        • TC

          #5
          Re: protecting VBA codes

          This has *got* to be XMVP, right?

          TC


          Larry Linson <bouncer@localh ost.net> wrote in message
          news:Psndb.1494 5$Wd7.8107@nwrd dc03.gnilink.ne t...[color=blue]
          > But, you should be aware that the concensus opinion of experienced Access
          > developers is that they can recreate a database application in very little
          > time if they can observe the user interface in operation. That is a
          > concensus opinion with which I am in agreement, just for the record.
          >
          > That's not to say you shouldn't use MDE, but only that you shouldn't[/color]
          believe[color=blue]
          > it will _really_ "protect you from having your application stolen".
          >
          > Larry Linson
          > Microsoft Access MVP[/color]
          (snip)


          Comment

          • Lyle Fairfield

            #6
            Re: protecting VBA codes

            "TC" <a@b.c.d> wrote in news:1064725011 .548634@teuthos :
            [color=blue]
            > This has *got* to be XMVP, right?
            >
            > TC
            >
            > Larry Linson <bouncer@localh ost.net> wrote in message
            > news:Psndb.1494 5$Wd7.8107@nwrd dc03.gnilink.ne t...[color=green]
            >> But, you should be aware that the concensus opinion of experienced
            >> Access developers is that they can recreate a database application in
            >> very little time if they can observe the user interface in operation.
            >> That is a concensus opinion with which I am in agreement, just for the
            >> record.
            >>
            >> That's not to say you shouldn't use MDE, but only that you shouldn't[/color]
            > believe[color=green]
            >> it will _really_ "protect you from having your application stolen".
            >>
            >> Larry Linson
            >> Microsoft Access MVP[/color]
            > (snip)[/color]

            Don can spell.

            --
            Lyle
            (for e-mail refer to http://ffdba.com/contacts.htm)

            Comment

            • rkc

              #7
              Re: protecting VBA codes


              "Lyle Fairfield" <MissingAddress @Invalid.Com> wrote in message
              news:Xns9404E31 375F9FFDBA@130. 133.1.4...[color=blue]
              > "TC" <a@b.c.d> wrote in news:1064725011 .548634@teuthos :
              >[color=green]
              > > This has *got* to be XMVP, right?
              > >
              > > TC
              > >
              > > Larry Linson <bouncer@localh ost.net> wrote in message
              > > news:Psndb.1494 5$Wd7.8107@nwrd dc03.gnilink.ne t...[color=darkred]
              > >> But, you should be aware that the concensus opinion of experienced[/color][/color]
              >
              > Don can spell.
              >[/color]

              They have redundancy in common.


              Comment

              Working...