Hi Doug and LaRetta,
Sorry for the late response, and thank you for responding! I tried Doug's suggestion, and when the permission is checked to allow the view of the data on the screen and not have it covered by the object, the object is still displayed (when the first criteria is also met i.e. the Leads::IsOnlineProposal = "No") The object then disappear when that field is set to "No", which is perfect, but for some reason its still not hiding the box when a user who has permission to view the data behind it is on the record. I hope that makes sense.
LaRetta, You are right, I did not consider the Find mode. I would need to incorporate that object to be hidden in find mode as well. Is that something that can also be scripted into the inspector hide portion?
As far as having a duplicate layout, that was my first thought as well! Unfortunately though there are over 600 fields that have relationships with other tables that I believe would need to be re associated as well wouldn't they? What i really wanted to do was create a separate module for these records and have them be moved from our Leads/Appointments Module to its own module Called Online Proposals via a script trigger (button click) to move them over to a separate area as they are now different style leads, and have only certain people be able to access that module. This seemed like a very large undertaking and for now at least if i could just hide that data from the users i want to hide them from that would be almost as good.
I really appreciate all the help! Thank you guys for bearing with me!