I know the fix for this has been gone over a few times but does anyone have a confirmation of whether it will be included in 6.2 or some patch for 6.1? I really would like to get this error cleaned up but I want it official. Thanks Scott