如何阻止库mde被重用 [英] How to stop library mde being reused

问题描述

嗨


我有一个与某些客户数据库一起使用的库mde，我找到了另外一个开发人员在进行一些维护工作时发现它的


在同一客户的旧数据库中，并已将其复制以用于她的

数据库。当然，我没有留下深刻的印象，这个故事还在继续。这是客户的错误

。


我假设她从客户数据库中获取了原始代码的副本

和正在研究如何使用库mde。对于这个客户

数据库提供了所有源代码而没有编译成mde。


还有一些其他情况我怀疑mde可能会在未经我许可的情况下重复使用

.


基本上，mde包含了我开发的一大堆功能

多年来我在为客户开发的系统中越来越多地使用它并且

并没有真正担心它会被淘汰，可以这么说，直到现在。


在这个小事件发生之后我已经考虑过了一些想法。


我想让一些客户将库重用于他们放在一起的数据库

，但是再次阻止这种撕裂。


我考虑过几个选项，但是对于

这个阶段的任何选择都不是很开心。


关于一个相当简单的停止方法的建议，或者至少

限制，这种情况再次发生将是赞。


杰夫

Hi

I have a library mde that is used with some customer databases and I found
out that another developer discovered it while doing some maintenance work
on an old database for the same customer and has copied it to use with her
databases. Naturally, I was not impressed and that story continues. It was
not the customers fault.

I assume she took a copy of the original code from the customers database
and is working out how to use the library mde from that. For this customer
the database is supplied with all source code and not compiled into an mde.

There are also a few other situations where I suspect the mde may be getting
reused without my permission.

Basically, the mde contains a whole bunch of functions I have developed over
the years and am using it more and more in systems developed for clients and
had not really worried about it being knocked off, so to speak, until now.

After this little incident I have given this some thought.

I want to allow some customers to reuse the library with databases they put
together, but stop this rip off happening again.

I have considered a few options, but am not really that happy with any at
this stage.

Any suggestions on a reasonably simple method of stopping, or at least
limiting, this from happening again would be appreciated.

Jeff

推荐答案

"杰夫" < JE ************ @ asken.com.au>在消息中写道

news：43 *********************** @ per-qv1-newsreader-01.iinet.net。 au ...

"Jeff" <je************@asken.com.au> wrote in message
news:43***********************@per-qv1-newsreader-01.iinet.net.au...

嗨

我有一个与某些客户数据库一起使用的库mde，我发现其他开发人员在进行一些维护时发现了它在同一客户的旧数据库上工作，并将其复制以用于她的数据库。当然，我没有留下深刻的印象，这个故事还在继续。这不是客户的错。

我认为她从客户数据库中获取了原始代码的副本
并正在研究如何使用库mde。对于这个客户来说，数据库提供了所有源代码而没有编译成
mde。

还有一些其他情况我怀疑mde可能是
基本上，mde包含了我多年来开发的一大堆功能，并且在为
客户并没有真正担心它会被淘汰，所以直到现在才说话。

在这个小事件发生后，我已经考虑过这个了。
我想让一些客户将图书馆与他们放在一起的数据库重复使用，但是再次阻止这种情况发生。

我考虑了一些选择，但我真的不那么开心

任何关于停止或至少限制这种情况再次发生的合理简单方法的建议将不胜感激。
<杰夫

Hi

I have a library mde that is used with some customer databases and I found
out that another developer discovered it while doing some maintenance work
on an old database for the same customer and has copied it to use with her
databases. Naturally, I was not impressed and that story continues. It was
not the customers fault.

I assume she took a copy of the original code from the customers database
and is working out how to use the library mde from that. For this customer
the database is supplied with all source code and not compiled into an
mde.

There are also a few other situations where I suspect the mde may be
getting reused without my permission.

Basically, the mde contains a whole bunch of functions I have developed
over the years and am using it more and more in systems developed for
clients and had not really worried about it being knocked off, so to
speak, until now.

After this little incident I have given this some thought.

I want to allow some customers to reuse the library with databases they
put together, but stop this rip off happening again.

I have considered a few options, but am not really that happy with any at
this stage.

Any suggestions on a reasonably simple method of stopping, or at least
limiting, this from happening again would be appreciated.

Jeff

我哈我总是发现通过编写一个足够差的标准代码已经足以阻止任何潜在的小偷了。这似乎是一种在Access社区中广泛使用的技术

。

I have always found that by writing code of a sufficiently poor standard has
been enough to deter any would-be thief. This seems to be a technique
widely used in the Access community.

有趣的方法，但不知道我的客户会同意。


杰夫


" Anthony England" < AE ****** @ oops.co.uk>在消息中写道

news：do ********** @ nwrdmz01.dmz.ncs.ea.ibs-infra.bt.com ...

Interesting approach, but don''t know that my clients would agree.

Jeff

"Anthony England" <ae******@oops.co.uk> wrote in message
news:do**********@nwrdmz01.dmz.ncs.ea.ibs-infra.bt.com...

杰夫 < JE ************ @ asken.com.au>在消息中写道
新闻：43 *********************** @ per-qv1-newsreader-01.iinet.net.au ...

"Jeff" <je************@asken.com.au> wrote in message
news:43***********************@per-qv1-newsreader-01.iinet.net.au...

嗨

我有一个与某些客户数据库一起使用的库mde，我发现其他开发人员在进行维护时发现了它为同一个客户处理旧数据库并复制它以用于她的数据库。当然，我没有留下深刻的印象，而且故事还在继续。这不是客户的错。

我认为她从客户数据库中获取了原始代码的副本
并正在研究如何使用库mde。对于这个
客户，数据库提供了所有源代码，而不是编译成mde。

还有一些其他情况，我怀疑mde可能是
基本上，mde包含了我多年来开发的一大堆功能，并且在为
客户并没有真正担心它会被淘汰，所以直到现在才说话。

在这个小事件发生后，我已经考虑过这个了。
我想让一些客户将图书馆与他们放在一起的数据库重复使用，但是再次阻止这种情况发生。

我考虑了一些选择，但我真的不那么开心

任何关于停止或至少限制这种情况再次发生的合理简单方法的建议将不胜感激。
<杰夫

Hi

I have a library mde that is used with some customer databases and I
found out that another developer discovered it while doing some
maintenance work on an old database for the same customer and has copied
it to use with her databases. Naturally, I was not impressed and that
story continues. It was not the customers fault.

I assume she took a copy of the original code from the customers database
and is working out how to use the library mde from that. For this
customer the database is supplied with all source code and not compiled
into an mde.

There are also a few other situations where I suspect the mde may be
getting reused without my permission.

Basically, the mde contains a whole bunch of functions I have developed
over the years and am using it more and more in systems developed for
clients and had not really worried about it being knocked off, so to
speak, until now.

After this little incident I have given this some thought.

I want to allow some customers to reuse the library with databases they
put together, but stop this rip off happening again.

I have considered a few options, but am not really that happy with any at
this stage.

Any suggestions on a reasonably simple method of stopping, or at least
limiting, this from happening again would be appreciated.

Jeff

我ave总是发现通过编写足够差的标准代码已足以阻止任何潜在的小偷。这似乎是一种在Access社区中广泛使用的技术。

I have always found that by writing code of a sufficiently poor standard
has been enough to deter any would-be thief. This seems to be a technique
widely used in the Access community.

我喜欢认为我写了很多有创意的原始代码。


有时我很生气，因为似乎有人拿走了我的代码。


但是在晚上我意识到这是我的兄弟的代码，开发代码，

教授TMK戴维森的代码，特里的代码，Getz的代码，迪米特里的

代码，Michka'代码，David'代码（偶数），Appleman代码，JA Green'

代码，rkc'代码，Danny'代码还有一千个其他人的代码，他们向我挑战，教我，激励我，向我展示，刺激我，

让我感到尴尬，攻击我并鼓励我。 br />

我意识到如果他们在我身上创造它我就不能拥有它。我必须让

它去。


但是明天我可以编写更好的代码。这消除了我的愤怒。

我喜欢认为这让他们高兴。



我只有一个追索权;我创建了一段更好的代码。

I like to think that I write lots of creative, original code.

Sometimes I am angry because it seems that someone has taken my code.

But at night time I realize that it''s my brothers'' code, Dev''s code,
Professor T M K Davidson''s code, Terry''s code, Getz''s code, Dimitri''s
code, Michka''s code, David''s code (even), Appleman''s code, J A Green''s
code, rkc''s code, Danny''s code and the code of a thousand others who
have challenged me, taught me, motivated me, shown me, stimulated me,
embarrassed me, attacked me and encouraged me.

And I realize that if they created it in me I cannot own it. I must let
it go.

But I can write better code, tomorrow. And this takes away my anger.
And I like to think it pleases them.


I have only one recourse; I create a better piece of code.

这篇关于如何阻止库mde被重用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！