To save some trouble, we tried to go ahead and make it unicode compliant. We are able to get it compiled, but we get these weird run-time errors that appear to revolve around malloc's ability to get us the necessary space. Any ideas on why the switch from TCHAR to WCHAR would create this mess?
Thanks, Ron Alleyne ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ otlkcon-devel mailing list otlkcon-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/otlkcon-devel
