There is similar verbiage available in any R&D Shop.  I wish I had a recent
copy I would supply it.   In short while you may come up with the idea and
they have paid for it, it then allows both parties to have the same rights.
But limited.  Also it then goes into the company side and limits the amount
of knowledge you transfer (Discloser Agreement) that it also has time
limits.  Mine are all 5 year agreements that renew any time funds are
transferred from one party to the next.  (Real short -  really it is about 5
pages)

 

I use a discloser agreement in many ways.  I like the fact it protects both
sides. 

 

 

 

 

 

So,  good luck and by all means should you need to contact me,  please do
so.

 

 

 

 

Paul

 

 

 

Not funny, but I am in the process of HUNTING a person down as we speak that
has not returned a computer / software / equipment.  He called and gave
notice and that was the last I heard from him,  the economy is that bad here
in Michigan.  I do not believe he has stolen any information from it.  But
.....         Perhaps it might be the reason I like the encrypt and compiled
w/expiration.  Now for 

 

 

 

 

 

From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Marc
Sent: Thursday, June 19, 2008 9:56 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Code copywrite

 

My app is different but this might work.

 

How about telling that you own the copyright but they have full rights

to use / modify it for their own use but they can't take your code and 

start selling the app or selling your code.

 

Marc

 

 

 

 

----- Original Message ----- 

From: jan johansen <mailto:[EMAIL PROTECTED]>  

To: RBASE-L Mailing List <mailto:[email protected]>  

Sent: Thursday, June 19, 2008 8:27 AM

Subject: [RBASE-L] - Code copywrite

 

Group,

 

Looking for some insights from people. I recently placed a copy of 7.6 on my
clients 

server so they would feel better about "if something happened to me" someone
else

could pick up the pieces.

 

They found what I have been placing in my rmd's at the top:

-- Title:        PurchaseRecon.rmd

-- Comment:      replaces old reconpur.cmd

-- Created:      Sep 2007

-- Author:       Jan D. Johansen 

-- Copyright C 2007 Dane Data Systems

-- Last Update

-- Uses Forms: PurchReconSelect,reconpur

 

Now they are upset because they thought they owned the code. In this case
the code is somewhat

hybrid. The original code was in 4.5 ++ (I think) and I have "borrowed"
sections of the original code during the upgrade. I have found traces of at
least 3 other people in the original. Of course I have rewritten sections
and supplanted with my own and borrowed from other people on the list. 

 

The header was placed mainly as an afterthought in the rmd's without much
thought to what it implied. 

 

So now - who owns the code? Is it the intellectual property of the developer
or since the client pays you for your services is it his? 

 

I know I should have spelled this out in an agreement but didn't think I
would run into anything like this (there I go thinking again). 

 

Any thoughts/comments greatly appreciated in advance (I'm offline for about
10 hours after I hit the send).

 

Jan

Reply via email to