Sorry for all the questions today: I have a graphic that features in all my dialogs. When the graphic is hit it brings up a version info dilaog: OnEvent>DIALOG_EVENT,FWarning,100,ShowVersion OnEvent>DIALOG_EVENT,LWarning,100,ShowVersion OnEvent>DIALOG_EVENT,MEAPDialog,100,ShowVersion SRT>ShowVersion...

Works perfectly thank you

Much easier than before as well with no worrying about string or numerical type etc.

Thanks guys, I'll get back to you if any problems arise. Looks straight forward though. Thank you again.

Thanks JRL but I can't see that working. The syntax doesn't make sense when compared to mine (which was originally provided by Marcus for v 9). My dialog is called: MEAPDialog, So in your examples you have mentioned 2 different dialogs. I will give it a try though of course and am very grateful for ...

Hi there, I am using the following type of code to grey out areas of my main dialog depending on certain criteria. //Get Handles LibFunc>User32,FindWindowA,dlgHwnd,TForm,MEAP Export Settings LibFunc>User32,FindWindowExA,edit1Hwnd,dlgHwnd,0,TEdit,%deffilename% LibFunc>User32,FindWindowExA,edit2Hwnd,d...

Thank you.

Tested and working fine now.

Would be interested to know what the problem was if it doesn't give away any secrets.

mtettmar wrote:Unable to replicate but have sent you a PM with a link to a debug version which will provide more information about the access violation.

Thank you Marcus I will forward all relevant info later this evening.

Ok I also tried removing the macros.dat file. No change. Some more info. This error only happens when running a script form the editor. If I close MS completely then double click on the macro file to run the script it executes perfectly. Once again steps to repro: Open the script in my first post in...

Hmmm ..I also had some access violation problems with MS10 beta that were never explained and I was also using Vista x64. See this post http://www.mjtnet.com/forum/viewtopic.php?t=4281. So far I am not having any issues with the general release of MS10. I also have another unresolved issue that occ...

Yes I have rebooted many times.

It is still 100% repro.

Would you like me to try with the beta again (I will need to re-download).

Please don't dismiss this as silly. I have a very stable and well maintained setup and a very decent system.

Once again I ask is anyone else using Vx64?

OK I did the following: Uninstalled all version (9 and 10). Removed all visible MJTNET entries from registry. Ran registry scan. Reinstalled v 10 only. Still getting the same error. Also MS will not quit. Although it shows that no macro is running after I have exited the macro (after the error). In ...

Here's a screeny just in case it's any help and my system info is in my signature:

I am using Vista 64 could this be the problem? It is 100% reproducible at the moment.

I will try un-installing and reinstalling tomorrow.

This does not appear to happen when the script is compiled.

Sorry I have to go to work now so can't follow this up until tomorrow.

Additional: Sorry - I am getting access violations when hitting buttons on many dialogues created with MS. For example I just tried with the Image Recognition test script: [code] /* This macro demonstrates the speed of the FindImagePos command. Run it and browse for a bitmap file previously created ...