It appears that this message is the default message for the 'WindowsDialogLimitMsg' property.  Why would this event be triggered when it doesn't appear any of his file names length are not exceeding this 32k limitation.