Protecting code

[G. Miller]

Hi all,

This is my first post on this newsgroup, and I'm sure this has been
discussed before. I've just converted a FoxPro database to Access/VBA,
and I'm wondering if there's a way to protect your server-based VBA
code from others with Access installed on their machines? If not,
should I consider using VB .net, and is a VB .net + Jet DB engine
program worth the extra effort?

I'm not sure on how big of a problem this would be, but the potential
is there.

Thanks in advance for any advice.

GM

[Salad]

G. Miller wrote:

Hi all,

This is my first post on this newsgroup, and I'm sure this has been
discussed before. I've just converted a FoxPro database to Access/VBA,
and I'm wondering if there's a way to protect your server-based VBA
code from others with Access installed on their machines? If not,
should I consider using VB .net, and is a VB .net + Jet DB engine
program worth the extra effort?
Convert it to an MDE.
I'm not sure on how big of a problem this would be, but the potential
is there.

Thanks in advance for any advice.

GM

[G. Miller]

That was easy. Thanks.
On Mon, 03 May 2004 19:18:46 GMT, Salad <oi*@vinegar.com> wrote:

G. Miller wrote:

Hi all,

This is my first post on this newsgroup, and I'm sure this has been
discussed before. I've just converted a FoxPro database to Access/VBA,
and I'm wondering if there's a way to protect your server-based VBA
code from others with Access installed on their machines? If not,
should I consider using VB .net, and is a VB .net + Jet DB engine
program worth the extra effort?

Convert it to an MDE.

I'm not sure on how big of a problem this would be, but the potential
is there.

Thanks in advance for any advice.

GM

[Lyle Fairfield]

gm*****@nospam-mobileregister.com (G. Miller) wrote in
news:40***************@newsgroups.bellsouth.net:

Hi all,

This is my first post on this newsgroup, and I'm sure this has been
discussed before. I've just converted a FoxPro database to Access/VBA,
and I'm wondering if there's a way to protect your server-based VBA
code from others with Access installed on their machines? If not,
should I consider using VB .net, and is a VB .net + Jet DB engine
program worth the extra effort?

I'm not sure on how big of a problem this would be, but the potential
is there.

At this very moment tens of thousands of us are plotting to steal your
code.

And when we do, we'll sell it to the highest bidder, probably some
international crime syndicate dealing in contraband intelligence of the
higest order.

Be careful. I've heard the CIA is sending a team to destroy it by fair
means or foul before enemies of the United States (aka "almost everyone")
can get their evil hands on it.

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

[G. Miller]

That sounds about right.

On 3 May 2004 20:14:40 GMT, Lyle Fairfield
<Mi************@Invalid.Com> wrote:

gm*****@nospam-mobileregister.com (G. Miller) wrote in
news:40***************@newsgroups.bellsouth.net :

Hi all,

This is my first post on this newsgroup, and I'm sure this has been
discussed before. I've just converted a FoxPro database to Access/VBA,
and I'm wondering if there's a way to protect your server-based VBA
code from others with Access installed on their machines? If not,
should I consider using VB .net, and is a VB .net + Jet DB engine
program worth the extra effort?

I'm not sure on how big of a problem this would be, but the potential
is there.

At this very moment tens of thousands of us are plotting to steal your
code.

And when we do, we'll sell it to the highest bidder, probably some
international crime syndicate dealing in contraband intelligence of the
higest order.

Be careful. I've heard the CIA is sending a team to destroy it by fair
means or foul before enemies of the United States (aka "almost everyone")
can get their evil hands on it.

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