I have a small problem. I have a database that I like, but my boss (URRG):mad: wants to give the database to another est. of ours. I know they are going to need to change certain items, so they are going to need Admin access to the database, but I need a way to be able to stamp my name in it, so that it can not be removed. I have thought about putting my name in the code sort of covertly but I need something simple that they all can see to let them know that "Hey that McCloud guy over there made this" and not Stupid Mcjerk. Any Ideas? :confused:

Sorry to be the bearer of bad news, but if it's something that you put together for the employer - as a part of your duties - then you don't have a "right" to do what you're wanting to do.

This being the case, you should speak to the manager about having it added.

I'm a little confused here. First, it might help to know what platform the database is in. But I don't understand why you feel the need to stamp your name on it. Did you develop it? If you did, as Rick pointed out, unless you did this on your spare time, it's the company's property not yours.

This was all used in Spare time using my own resources. I showed it to my boss and got the OK to use it in the company. But now... I just don't know. Thinking about scraping the whole thing.

P.S. MS Access 2003

Ok, there is no foolproof way to do this. You can create a splashscreen that lists your name. You can make this a hidden form so it only displays briefly and then hides again. Or you can add an author's table with your name and the creation date and hide that table. There are other things along similar lines, but nothing that's foolproof.

Your boss knows where it came from, isn't that enough?

Yea I suppose so, but I just don't trust those other guys. There shady as hell. Any way, I talked it over with the boss and the best way I can think of this is to redisign the database (with there logos and what not) and lock it down. They can have all the stuff they need, but they are not getting the admin access to in.

Thanks everyone.

"Ladies and Gentelmen, take my advice. Pull down your pants, and slide down the ice."

:D

That would be the best way. Split the database, make the front end an MDE file. Then they can't make any design changes.