Kate,
you are using task 29 to represent not just the placing of the order, but also the lead time. I would make a milestone task (zero duration) named "Place Order For Wood Flooring" to represent placing the order, and this milestone is a FS0 predecessor to the
lead time, which I would call "Wait For Wood Flooring". I would also make another milestone task called "Deliver Wood Flooring". Now, the order can be placed early, and the lead time starts immediately after, and is FS0 predecessor of "Deliver Wood Flooring",
and that is a FS0 predecessor of "Install Wood Flooring". The installation task has other predecessors which are whatever the construction task is that must finish before the flooring can be installed.
Now, the critical path will run through the construction tasks, which means that the order, wait and deliver are on a path which has float, so they are not on the critical path. This means they can be delayed, or at least placing the order can be delayed,
up to a point before they use up their float and become critical. Every task which has float has an earliest start date and and earliest finish date, and a latest start date and and a latest finish date. You can see these dates in the schedule table. The date
you are looking for is the latest start date of the order task. It has been calculated for you by MSP. It is not displayed on the default Gantt Chart view because that view draws the bars from the earliest start to the earliest finish. If you choose a different
view, say the Detailed Gantt chart, that will display the float (slack in MSP).
You are running into problems because you do not have a clear understanding of the critical path method, and that is essential for construction planning.
Any help?