anixon

Thanks for the prompt response very much appreciated. Ant..

I have been looking through the Outlook UDF's for a script that supports a process which simply saves any file/s attached to an email to default folder and then on completion of that process delete the email and its attachment. I am ok with most of the prcoesses however the method of dealing with the attachment escapes me. If you can point me in the right direction that would be very much appreciated. Ant..

Perhaps 'DisplayVersion" is called "DisplayName" which is the case for AutoIT

Hi smartee Very nice including the elegant method you have used for stripping the $ and *.. checksum from the NMEA sentence. I probably would have approached it stringleft stringright and tested the value probably achieving the same result but to much code. What is interesting with coding is what sometimes appears to be the almost endless possibilities of achieving the same result. Cheers Ant..

Happy to test your code if you post it here rather than a download. Ant:)

Thanks whim that works on the example. I will check it further to make sure that it works on all NMEA sentence types. I would like to confirm that your help is very much appreciated. WTF is a NMEA sentence? Well the short answer is its the standard protocol used by a GPS receiver to create a sentence from data streamed from a GPS Satellite. The checksum is calculated and added to each sentence and is used to confirm that the data contained within each sentence has not been corrupted. Thanks again Ant.. I have tested the code on the following NMEA sentences and it works perfectly ;$GPGGA,123519,4807.038,N,01131.000,E,1,08,0.9,545.4,M,46.9,M,,*47 ;$GPGSA,A,3,04,05,,09,12,,,24,,,,,2.5,1.3,2.1*39 ;$GPRMC,123519,A,4807.038,N,01131.000,E,022.4,084.4,230394,003.1,W*6A ;$GPGLL,4916.45,N,12311.12,W,225444,A,*1D Cheers Ant..

I'm struggling with this one. Based on the NMEA checksum calculator method can anyone confirm that this code produces the correct checksum 'x38' for the string 'a9' $value1 = "a" and $value2 = 9. I have yet to write the loop to xor all the values that would normall make up a string. What this calculates is the checksum on the assumption that their are only two chrs in the string. $value1 = "a" $value2 = 9 Msgbox(0,"",BitXOR(asc($value1), asc($value2))) Msgbox(0,"",StringToBinary(BitXOR(asc($value1), asc($value2)),1)) Help is always appreciated Ant..

The Visual basic code converts the character to bytes how is that achieved in AutoIT?

Calculating the checksum is the representation of two hexadecimal characters of an XOR of all characters in the sentence between – but not including – the $ and the * character. Lets assume the following NMEA sentence: $GPGLL,5300.97914,N,00259.98174,E,125926,A*28 In this sentence the checksum is the character representation of the hexadecimal value 28. The string that the checksum is calculated over is GPGLL,5300.97914,N,00259.98174,E,125926,A To calculate the checksum you parse all characters between $ and * from the NMEA sentence into a new string. In the examples below the name of this new string is stringToCalculateTheChecksumOver. Then just XOR the first character with the next character, until the end of the string. Below you find a code example in Java script, VB.Net and C#. In Java script: var checksum = 0; <br style="margin: 0px; padding: 0px; line-height: 1.4em; font-size: 9px;">for(var i = 0; i < stringToCalculateTheChecksumOver.length; i++) { <br style="margin: 0px; padding: 0px; line-height: 1.4em; font-size: 9px;"> checksum = checksum ^ stringToCalculateTheChecksumOver.charCodeAt(i); <br style="margin: 0px; padding: 0px; line-height: 1.4em; font-size: 9px;">} In C#: int checksum = 0; <br style="margin: 0px; padding: 0px; line-height: 1.4em; font-size: 9px;">for (inti = 0; i < stringToCalculateTheChecksumOver.length; i++){ <br style="margin: 0px; padding: 0px; line-height: 1.4em; font-size: 9px;">checksum ^= Convert.ToByte(sentence);} In VB.Net: Dim checksum as Integer = 0 <br style="margin: 0px; padding: 0px; line-height: 1.4em; font-size: 9px;">For Each Character As Char In stringToCalculateTheChecksumOver <br style="margin: 0px; padding: 0px; line-height: 1.4em; font-size: 9px;"> checksum = checksum Xor Convert.ToByte(Character) <br style="margin: 0px; padding: 0px; line-height: 1.4em; font-size: 9px;">Next What is left is to transform the checksum into two hexadecimal characters, and that is it. In VB.Net and C# you can use the ToString function for this, e.g. strChecksum=checksum.ToString(“X2”). Can this calculator be coded in AutoIT and is their an example available? Replies are always appreciated Ant.. )

It is a multi purpose financial analysis tool designed so that a user can perform a number of different task specific annuity calculations to obtain a pre-commitment heads up as to actual cost of any financial accommodation under consideration. Ant..

All I can say is that I have a working prototype of a task specific application which I have developed in AutoIT that not only deals with the look and feel but also the functionality a working specification if you like. Unfortunately I am not an iOS code cutter so I was look for someone that might be interested in a collaboration to convert the work I have completed into a 'Free' iPhone/iPad Application. I am sure you would understand that a public disclosure as to the more specific details of the project is not possible where commercial in confidence, copyright and , intellectual entitlements of those that may seek involvement need to be preserved. Ant..

I not sure whether it is correct to post this request in this forum and if not I apologise. Put simply I am seeking an introduction or referal to a person who can convert an AutoIT script into an iOS iPhone/iPad/iPod Touch application. If anyone knowns of anyone who has the skills and is looking for an exciting project and who wants to convert some spare time into an opportunity then I can be contacted through this forum for more information. Help is always appreciated

Perhaps I did not explain the FileOpen as well as I could. Put simply the Notebook had the file open displaying its contents before that file open by the previous FileOpen process actually appeared in the file manager window. I guess I was expecting that the file would be created appear in the file manager before it was available to be opened by the text editor. Whether that indicates a timing issue that requires some sort of wait statement I will leave to others to comment. I have noted on past occasions that a cold boot of the system sometimes remedies unexplained issues. Having rebooted my always on system and can confirm that the code as I have written which pretty much mirrors your example works without issue. I therefore have no definitive answer as to what was, might have been, or was the issue that cause the symptom . I have noticed however that in recent times the File Manager has on occasions become particularly slow which given that my operating system runs on a SDD may indicate an issue unrelated to AutoIT. In the same environment Photoshop CS5 a heavyweight application shows no degradation in launching or processing performance. All of which I have for the time being put down to just another one of life's mysteries Ant

Thanks for that that code works without any issue although I did notice that the file opened before it appeared in the file manager. Is it likely that you could corrupt the script directory or the 'Fred' file if you incorporated a FileSetAttrib($Fred, "-RS") where the file was not set as +RS Edit: Or perhaps the mistake I made was changing the attributes after the file was open.. 2nd Edit that did not make a difference at all so my issue at the time was not created by the FileSetAttrib code.. humm ..

You are correct the file must be closed before processing the FileDelete and in such circumstances the issue persists. This is a totally new aboration which seems to have appeared and may be related to updates published by Microsoft althought I cannot say with any certainty that it is related. Perhaps if some also running a Windows Vista desktop which is uptodate with every update patch published by Microsoft could perform a simple test to see if it is a system specific issue. Ant