HappyJoyAwesome

I've created some macros to keep contact lists up-to-date. Unfortunately the list of contacts is derived from software that doesn't allow email addresses to be associated with each contact (it's old). So I've generate a tab delimited list from the software's database and I want MEP to compare this with another tab delimited list which has the same fields, except email addresses associated with each record/line. So with each macro run we have a newlyGeneratedContactListWithoutEmails (aka "NEW") file which we need to compare to TheLastListWithEmails (aka "OLD") file. This is because new contacts continually get added, some get edited, and the staff need a way to manually add an email for each CONTACT/LOCATION combination, and this can be done with a nifty CSV viewer/editor. Once the comparison is done and the emails are matched to the correct row, the row is save/appended to a newListFile. The logic of the macro is something like the following: ASCII File Begin on NEW ASCII File Begin on OLD IF %CONTACTfromNEW% = %CONTACTfromOLD% AND IF %LOCATIONfromNEW%= %LOCATIONfromOLD% IF %OLDLISTARRAY[x]% Contains "@" SET STRING %NEWLISTARRAY[x]% TO %OLDLISTARRAY[x]% GoTo UpdateRecord END IF END IF ASCII File End Label: UpdateRecord SET STRING %newContactListWithEmails% to %NEWLISTARRAY[1]%<TAB>%NEWLISTARRAY[2]%<TAB>...etc. IF Not File Exists "newListFile.txt" Modify String: Save %newContactListWithEmails% to "newListFile.txt" ELSE Modify String: Append %newContactListWithEmails% to "newListFile.txt" END IF ASCII File End The above works correctly but is horrendously slow. We're talking about lists with 900 rows in the text file to compare and it outputs a new line/record to the new file about once every minute. How can I make this faster? I would normally use SQL for something like this but I don't have bulk insert permissions.

I'm not sure how I'd be able to create MEX and MXE files to upload and demonstrate this as it would have to go through the ~100 macros (and all the system specific scripts) to iterate through one cycle. I wish I knew how I suppose this post is more an attempt to see if others have experienced something similar or may be familiar with the problem and/or how to fix it based on the description alone. ONE THING I FORGOT TO MENTION: The MXE file sits on a network drive (as does the MEX and all the other relevant bits). We've always run it from one designated computer, but the macro files that have been developed have always sat on a network drive. Could this have something to do with it? Just thought I'd ask first before I attempt to reconfigure it all to work on a local drive.

Hello All, I'm new here and I didn't want to necrobump an old thread. I have been continually adding functionality to a set of almost 100 macros that work together like a system that automates a whole bunch of tasks. This runs on a dedicated computer, and the idea is to run it and let it do its thing for several days. All of the macros are "No activation" macros, there is one main macro that is set up as an infinite loop in which other macros are called, and I export this macro as playable for the whole thing to be manually run on demand. I've developed this over the span of about a year, and it's been working great, however recently I'm getting a "Macro does not exist (0x000E)" error when running the playable macro. - I know the macro exists - It is spelled correctly in the Macro Run command - The optional macro file field is always empty for any Macro Run command - I never experience this error when I run it from the script editor (test run), and we've resorted to running it this way (however this is not suitable for us) What's funny is that, when I run the playable macro, it all works fine for the first cycle of the infinite loop; the error only pops up the second time around. Just for testing purposes, I disabled the Macro Run command that was causing the error, and the error popped up for a different Macro Run command. Hence, this problem is not specific to that single specific command. I am using Macro Express Pro 4.2.2.1 on Windows XP SP3 Any suggestions to determine the cause of the problem and fix it?