Leaderboard

Based on the Outlook UDF written by wooltown, we (wooltown and I) decided to extend the functionality of the Outlook UDF. As the OutlookEX UDF ("EX" like "extended") has a completely different approach compared to the Outlook UDF it's a complete rewrite. We would like to discuss the design of the UDF with the community. Every feedback, function request etc. is highly welcome. As soon as the discussion shows that we are on the right track we would like to release an alpha version for everyone to test. So please don't be shy and post what you think of this UDF or what functions you need! Every item in Outlook is uniquely identified by EntryID and StoreID. The default StoreID is your inbox Every item has properties to describe the item (subject, startdate ..) and methods to act upon the item (move, delete …) The search and action functions are now separated. As an example the user first searches for the items to be deleted and then calls the delete function If a method can be used for more than one item type (e.g. mail, calendar and notes) the function is called _OL_ItemXXX else the function is called _OL_CalendarXXX The number of properties you can get or pass to most functions is not limited by the number of parameters defined for the function. Properties can be passed as parameters (up to 10) or in an unlimited array as parameter 1 The UDF allows to access all kind of folders (see the following listing). Folders can be passed by name or as an object to a function A lot of testing is still needed as we have written and tested the functions using Outlook 2002 SP3 and Outlook 2010 "wrapper" or "shortcut" functions will be available to let you do all tasks in one go e.g. _OL_Wrapper_SendMail for all functions above. Documentation: The documentation for this UDF (aside from the docu in the UDF itself) will be placed in the AutoIt Wiki. So we can easily modify the docu without releasing a new version each time. There will be pages describing the UDF in general and pages for individual item types (like mail) with detailed information and a lot of tips & tricks. Tested with Outlook 2003 and 2010. Some users reported that it works with Outlook 2013 as well. Starting point: http://www.autoitscript.com/wiki/OutlookEX_UDF_-_General Download

This is more of a question than a suggestion. Rather than read partial strings, would it be faster or slower to use _ArraySearch() after sorting both arrays first? This way wouldn't identify partial matches Something like: (untested) _ArraySort($Array1,0,0,0,0) _ArraySort($Array2,0,0,0,0) For $i = 1 To UBound($aArray1) - 1 $match = _ArraySearch($Array2, $Array1[$i]) If @error Then ContinueLoop FileWriteLine($hDiff, "File1: Line" & $i & ":" & $aArray1[$i] & " File2: Line " & $match) Next It could be that this is a horrendous way to do it, as I say I really don't know, but I'd be interested to hear.

The reason some lines are compared twice is because the first part of line 571 in file 1 matches the first part of both line 414 and 415 so line 571 in file 1 gets compared with line 414 and 415 in file 2. PS: If this is somthing you are going to have to do on a regular basis the script can be made considerably faster by sorting the the arrays and walking the index on the second array manually rather than looping through the entire array for each line. You could also add a lttle GUI added for the user to select the input and output files and show progress.

I thought you gave this forum one last chance Is the one extra last chance now, after you got no help in bypassing other security measures?

Lyoko, As the OP has not been online here since Nov 12 2010 I doubt he will reply. What have you tried so far that does not work? M23