Please help

I know that I should not ask this but is there any code that you can use to protect yourself against not being paid for work completed? I have sub-contracted for a month now with a company and they keep telling me to wait to cash my cheques, so I contacted the local labor board and they have several cases against this company but they cannot catch them because they keep moving offices. So is there any hidden code that I could insert into the work that I have done so far that would stop the pages from working and they I could deactivate it once paid?

Thanks
Tim

kloodge it up a bit - throw in a few functions that will lock anyone out who is not you! - Comment out these "timebombs" until they either put up or throwdown. Somethign as simple as a block of SessionCode at the top of a page taht checks an offsite database for a value (your database), if the value doesn't exist:
die("You need to pay me before you can use this feature. - my@email.com")

for example:

how about dont do the work! Its as simple as that, too risky...

one thing that would work well, is working off of a server that is local, not the client's remote machine.

You can program all the timebomb and offsite checks you want, but they're easily removed unless you're working with idiots.

Getting a solid contract and placing work on one of your own servers is the best way to handle this. They see the results or snippets of the code as required, but don't get it all installed until it's paid for. Anything less than this and you run the risk of getting screwed... again...

---John Holmes...

This was an hourly employment position so as the employer he required me to keep the files on his server, I am contacting a lawyer not sure if it will help, but no wonder we are all requiring deposits and such for work.

Tim

Moved from the PHP Development forum.

If they are hiring outside help, how likely is it they have someone who can root out and remove all the traps?

well, then they fall into the "working with idiots" category...

Keep in mind that doing the work and getting paid are two issues. Unless you have in your up-front contract that you are going to write code that remains incomplete (i.e., has a logic bomb in it) until the check clears, deleting/interfearing with the code as it exists is probably illegal (though, obviously, if they are already dodging the law then it is unlikely they will call the cops). There was a similiar thread very recently, you should look for it and read it.

It almost definitely is. There are several areas of applicable law and it's probably covered under each. It's sabotage (prison). It probably falls under laws newly created to jail hackers who propogate viruses or DOS attacks (prison). As far as business law there is a good case for breach of good faith agreement (lawsuit). And several others I could name that may or may not apply.

If you play your cards correctly you have a legally binding contract and if you are not paid, then you're the one that does the litigating for failure to pay for services rendered.

To top it off, you're an hourly employee. You don't own anything done on their clock (as nor do I own the miles of code I write day in, day out for my employer - it's their's that's why they pay me). If they fail to pay you, you have a simple case that a local government agency will usually be glad to investigate.

you should check your appointment letter and the clause mentioned thereupon which might you have signed as token of acceptance, before proceeding to a labor board.

Before that I shall suggest you try to solve the matter by mutual understanding with you and your employer rather than moving for legal assistance.

It may possible that