Gizmo, I think it's something about the last com error you posted (LiteX.LiteStatement.1) that is causing the scan to take longer. I believe that after the error posts, the builder updates all files after that point, even if they have been scanned already. It has to be a certain file causing this because the error happens in the exact same place of the build everytime. I have yet to find the file or group of files causing this error, but I will post when I find it.
At least the scan completes now...



LinkBack URL
About LinkBacks





Reply With Quote




Bookmarks