Yes no probs, zipped up and on it's way. -----Original Message----- From: j-say-bounce@xxxxxxxxxxxxx [mailto:j-say-bounce@xxxxxxxxxxxxx] On Behalf Of Pranav Lal Sent: Wednesday, 28 July 2010 4:53 a.m. To: j-say@xxxxxxxxxxxxx Subject: [j-say list] Re: Macro error Justin, Can you send me your commands file in the *.dat format off list? Pranav -----Original Message----- From: j-say-bounce@xxxxxxxxxxxxx [mailto:j-say-bounce@xxxxxxxxxxxxx] On Behalf Of Justin. Tate Sent: Tuesday, July 27, 2010 2:55 PM To: j-say@xxxxxxxxxxxxx Subject: [j-say list] Re: Macro error Ok so I’ve repaired all programs without success. The steps were as follows in order. Repaired Dragon 10 Repaired Jaws Repaired J-say I also redid the J-say configuration including the part that readies the Dragon profile just in case this was messed up in the process. It’s really puzzling as everything else seems to work fine, at least what I’ve tested so far anyway. Something’s clearly getting in the way, I just don’t know what. The error message indicates the use of the mycommands editor to remedy the problem, has anyone any tips for using this function? Regards Justin ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- Hey thanks for the reply Ed, no I haven’t tried re-installing all programs, I was just curious as to which application was causing the macro error, and if there was indeed a compatibility issue, as I would rather try and sort that side out first then spend time re-installing only to have it break again. At this stage I have nothing else to go on, so will re-install all apps and let you know how it goes. Thanks again for your help. Regards Justin ---------------------------------------------------------------------------- --------------------------------------------------------------- Justin-The fact that this was working and has now stopped working is curious. You did not indicate whether you had tried a Repair of Jaws, Dragon, and J-Say Pro. If not, I think that would be an advisable next step to see if you couldn't restore the functionality to this command. If you've are redundant re-post, and if you haven't given a try and then if that doesn't result why not repost at that time. -ed. ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- ----------------- Hi there, I’m really hoping that one of you can help me out here, I have a frustrating issue which I still have not been able to resolve, I’ve posted here before regarding this issue but perhaps didn’t show enough detail in my posting so here goes J There is a macro error when giving the command email (whomever) this function previously worked and now does not. The macro error reads: The macro contains the error. My command: :”Email Justin” Line: 3 Position 12 Description: invalid instruction. – Please, use Mycommands editor to make the appropriate corrections I have tried deleting the .dat file and re-creating but has the same results, this is not happening to all the stored J-say contacts. This is the contents of my justin.dat file LHSP[1]‡ [1] New Message to JUSTIN ________________________________________ ySub Main DllCall "MSGW1004","JFWRunScript","PleaseWait" AppBringUp "mailto:Justin.tate@xxxxxxxxxxxxxxxxxx"; End Sub EMail JUSTIN ________________________________________ >Sub Main SendKeys "Justin.tate@xxxxxxxxxxxxxxxxxx" End Sub \Email I haven’t been able to find a pattern between the ones that do work and the ones that don’t, so am kind of stuck at the moment. The specs of the setup are: Windows XP service pack3 Office 2007 Jaws 9.0.2.2169 Dragon 10 J-say 6.2 3gigs of RAM Computer brand and model: HP dc7900 CMT E8400 3Ghz160GB We are using a Parrot headset which uses its own sound card. Any help on this would be greatly appreciated, someone suggested last time I posted about this that it was possibly a version conflict between the 3 programs, we received this from a distributer who assured us that they would work together, unfortunately they are no longer so if anyone could confirm that that this is the problem that would also be something to look at. Kind Regards Justin __________ Information from ESET NOD32 Antivirus, version of virus signature database 5315 (20100726) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 5318 (20100727) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 5318 (20100727) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com