TrainingExcellence
New Member
- Joined
- Apr 6, 2017
- Messages
- 10
- Office Version
- 365
Question for self-employed developers: If I develop an application in Office for a client, who owns what, and what can I reuse?
I've read a number of articles that talk about how the client needs to be sure they own both the finished product and the source code, but does that mean I, the developer, cannot reuse any components of the application for other projects? Most, if not all the code I would use could be found on forums, so I would think I could use that freely. And anything else I would develop would simply be a manipulation of existing objects available within the Office application (i.e. control buttons, listboxes, charts, etc.). So at what point would a client own any of those things?
Let's say I built an application for a lender that is used for processing mortgage applications, and the client insists that they own everything about the application. Later, I have a manufacturing facility that needs an application for tracking incidents and OSHA recordables. If I find there are components of the previous mortgage application that could be modified and used for the manufacturing facility's project, could I use those elements? Two different companies with two different applications? Or would the mortgage company have dibs on it?
I guess I just don't understand how someone can own the components of an application, and at what point something goes from being open-source to custom. Do I have to explicitly state in the contract that I reserve the right to replicate components of the application provided it doesn't infringe on the non-compete? Can anyone shed some light on this problem?
Thanks!
I've read a number of articles that talk about how the client needs to be sure they own both the finished product and the source code, but does that mean I, the developer, cannot reuse any components of the application for other projects? Most, if not all the code I would use could be found on forums, so I would think I could use that freely. And anything else I would develop would simply be a manipulation of existing objects available within the Office application (i.e. control buttons, listboxes, charts, etc.). So at what point would a client own any of those things?
Let's say I built an application for a lender that is used for processing mortgage applications, and the client insists that they own everything about the application. Later, I have a manufacturing facility that needs an application for tracking incidents and OSHA recordables. If I find there are components of the previous mortgage application that could be modified and used for the manufacturing facility's project, could I use those elements? Two different companies with two different applications? Or would the mortgage company have dibs on it?
I guess I just don't understand how someone can own the components of an application, and at what point something goes from being open-source to custom. Do I have to explicitly state in the contract that I reserve the right to replicate components of the application provided it doesn't infringe on the non-compete? Can anyone shed some light on this problem?
Thanks!