When using Lansweeper, particularly when constructing reports, we shouldn't have to concern ourselves with what operating system an asset is running. I perceive this as a flawed database design. Sure, there would be tough calls and compromises in a redesign, but at the end of the day a well-written data dictionary would describe those decisions. It's a 
wall I keep having to work around. As Ronald Regan might have said, "Lansweeper, tear down that wall!"
Alternatively, or better yet, in parallel to its work on a new database design, Lansweeper should focus on clearly and consistently documenting how to pull the current pieces of data together. The statement "combining these tables requires you to write UNION queries" should be changed to "here is a complete library of the UNION queries Lansweeper has written."
wall I keep having to work around. As Ronald Regan might have said, "Lansweeper, tear down that wall!"Alternatively, or better yet, in parallel to its work on a new database design, Lansweeper should focus on clearly and consistently documenting how to pull the current pieces of data together. The statement "combining these tables requires you to write UNION queries" should be changed to "here is a complete library of the UNION queries Lansweeper has written."
