Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
Currently doing some work on a high-profile application for a client. We've got the application running nicely, but it causes problems with another, reasonably high-profile application that's been around for a while.
So, we're trying to work out how to get both applications working together. I proposed a simple fix on the other application. This was rejected by a cowboy contractor, who says, effectively, it's up to us to get our application working, without changing theirs. Thing is, it's their application that has the fault, but it's only revealed when ours is implemented.
Same client, same system. Hopefully a project manager will giving him the twatting this "contractor" needs.
Leave a comment: