formula and query protection

[Guest]

I work for an organization that has almost 30 offices, not counting the
district offices. I have been developing my database over the past year
working out kinks and adding enhancements. I have learned that another
district has hired a consultant to create a similar database. They would
like a copy of what I have. Since I have not pushed my database up to the
higher levels yet, I do not want this consultant (who knows nothing about our
field of business) (and is getting paid) (I have built mine in my down time
from my day to day tasks) to take my ideas, queries, reports, etc. I don't
mind working with someone. As a matter of fact, if my database gets pushed
up the ladder, I will be needing a consultant to help with the really tricky
stuff. Any suggestions on how to protect what I have now? And due to the
size of the organization I work for, should the "powers" approve of my
database, if and when a consultant is needed, it will be a very huge
undertaking for a consultant to get this available for all offices within our
organization.

 

[David F Cox]

In the UK it used to be the case that the organisation you worked for owned
the intellectual property rights to anything related to their business that
you have developed. I am not sure of the law here or elsewhere now.
I wish you luck with the consultant.

 

[Granny Spitz via AccessMonster.com]

I have learned that another
district has hired a consultant to create a similar database. They would
like a copy of what I have.

If the consultant is an expert, chances are your database will be used as an
example of what the company needs in the software, which will cut down on the
costs of gathering requirements for the software he develops. In this case
the consultant will *start from scratch* with his own design, data
architecture and all. Even if the final product *is* an Access database,
very little, if any, will be built from your example. OTOH if he isn't an
expert and the other district stays with Access, chances are he'll fix a few
things but mostly just add to what you've built. The things he fixes will be
the *fluff*, not the foundation.

(I have built mine in my down time
from my day to day tasks) to take my ideas, queries, reports, etc. I don't
mind working with someone.

It sounds like you think the database is *yours*. Under US law it *might* be
if you built it entirely at your home office and you've previously signed a
contract with your employer that software you build is not owned by the
company. In point of fact, it usually comes down to *work for hire* status.
Is the employer paying half of your social security taxes and requiring you
to substantially follow their direction on when you work, how you work and
where you work? If they do the products of that work belong to the employer.

Even if you developed the database *after hours* (after your normal 8 hour
day), if you developed it on their site with their computer equipment and
network, most of the time the software belongs to the employer unless some
other written agreement exists allowing you to own what you develop *on your
own time* at *their site*. If you developed this database during your normal
working day, even if you finished your work early and could net surf or do
productive work and chose to build it instead, the database belongs to the
employer unless you have a prior written agreement that states otherwise.

Any suggestions on how to protect what I have now?

If you convert it to an MDE they won't be able to see the code, but you'll be
branded as *uncooperative* if you don't give them the MDB. You can't hide
anything else in the database unless you apply User level security, but if
you don't provide the MDW, a login ID and password, you'll be branded as
*uncooperative* too. If you want to keep your job, I suggest you cooperate
unless you *know* you own this software. If the final project is a success
and you've helped you'll get some of the credit, which you shouldn't neglect
to point out at your next performance review.

 

[Guest]

Thank you so much for the advice. I know that the database is not mine and
belongs to my employer (I have there logo all over the place). But you know
the competition thing. I started here in an entry level position and this is
will really help me launch my career. As a matter of fact, the OIS dept here
knows nothing about a database. It will be something we can get to the top
and say, see what we did and did not cost any extra money (in our district)
and the other district paid for the something that is not as good as ours.
Plus any innovative ideas that save time and $$ will put some $$ back into my
wallet, which is always a good thing.

My supervisor here told me if you don't look out for yourself, no one else
will.

I personally would not mind sitting with the consultant from the other
district, and pick their brain as well.

 

[Granny Spitz via AccessMonster.com]

As a matter of fact, the OIS dept here
knows nothing about a database.

That usually makes the IT department angry, because they don't want non-IT
people building database applications. They've witnessed a lot of database
disasters built by laymen who knew nothing of normalization, queries,
security, etc.

My supervisor here told me if you don't look out for yourself, no one else
will.

Your supervisor is 100% right.

I personally would not mind sitting with the consultant from the other
district, and pick their brain as well.

If the consultant is an expert, you'll benefit more from your meetings with
him than he will.