Reece,
Both the solutions in the first two posts will give you what you want.
I strongly advise you setup a dummy project of 6 to 10 activities and trial these solutions thoroughly before applying either. -You need to understand fully the implications before you risk using them on a live project, and your last post suggests you don't understand them very well at the moment.
Personally, I would use mandatory constraints rather than lag, as you would have to manually adjust the lag values after each update to maintain the float calculations you want, whereas mandatory constraints will not suffer from this. Mandatory constraints are also easier to toggle on and off, so you can turn them on for reporting purposes, and then take them off again to see the "true" critical path running through your project and actually plan the job properly.
Be aware though that both the solutions presented run the risk of generating "false" dates downstream of where you add the lag or constraint. -Which is why it's so important to know what you are doing when you use them.
Cheers,
G