Jump to content
Macro Express Forums

alexlimbert

Members
  • Posts

    34
  • Joined

  • Last visited

Posts posted by alexlimbert

  1. The ADD, PROPERTIES, and DELETE button shortcuts in the Variable Tab do not work. You can push ALT+A, ALT+P, or ALT+D OR CTRL+A, CTRL+P, or CTRL+D, but you won't get the desired effect.

     

    ALT+A opens properties (not sure how this happened as there is no A in properties)

    ALT+P opens the Scope Tab (ALT+P also represents the Scope Tab shortcut)

    ALT+D opens the Debug Menu (ALT+D also represents the Debug Menu shortcut)

  2. 2) I just tested your question number 2 and I didn't note any problems. That is, both ran simultaneously and the shortcut keys I setup in Macro Express launched my Macro Express macros and the shortcut keys I setup in Macro Express Pro launched my Macro Express Pro macros.

     

    Now that the results appear that both can run simultaneously, I will probably keep both apps running rather than importing old macros into Macro Express Pro.

     

    Alex

  3. I'm kind of very lost. I would like to do Scasper's suggestion, but I am not sure what is meant:

     

    Variable Set Integer %N1% to 10\\\\\\\\\\\\\\\\\\\\\\\\\\Sets N1 to 10 (this will cause your list to start on %T10%) What exactly starts at %T10%?

    Text File Begin Process: "textfileprocess001.txt"

    Variable Set String %T2% "<TVAR2:%N1%:01:%T1%\s>" \\\\\\\\\\\\\\\\\I don't know direct editing, what does this stand for (or look like) in scripting editor?

    Run Macro in Variable %T2%

    Text Box Display: Text File Process 001

    Variable Modify Integer: Inc (%N1%)\\\\\\\\\\\\\\\\\ Not sure what this is.

    Text File End Process

  4. Excel does add extra characters when copying a cell to the clipboard. Most likely this is what you are seeing in your test.

     

    Copy a cell to the clipboard and save to a text string variable. Then use the Variable Modify String - Trim command. Save the variable to a text file - Variable Modify String - Save to Text File. Open in the Hex Editor and the 0D0As should be gone.

     

    Do the same thing without the Trim and you will see the 0D0As.

     

     

    Thank you for the kind recommendation. In this case, unfortunately, I am setting up a database with 30,000 - 40,000 records. Since the database is Excel, the program receiving the field we are talking about has a bunch of carriage returns. I wonder what would happen if I stripped the HTML Tags out. I'll give that a try.

  5. The macro appears okay, but I am seeing something strange. When I save the CRLF stripped text to a text file, there are no more CRLFs or 0D0As. However, when I save the text to a column in a comma delimited CSV file, the column retains most (perhaps all) of the CRLF/0D0As that existed.

     

    I double checked and tested to see if this was happen was true by saving the stripped text results to a text file. I opened the text file in the hex editor and there were no 0D0As anywhere. I copied this text to the clipboard and pasted it into an MS Excel cell and the CRLFs returned. I copied this back to a text file, and reopened this text file in the Hex Editor and the 0D0As were back.

     

    I still wonder if HTML has something to do with this, or perhaps Excel.

  6. I'm not sure why but only some CR/LF's are replaced

     

    // Set Environment variable "CRLF" to cr/lf characters

    Variable Set %T2% to ASCII Char of 10

    Variable Set %T3% to ASCII Char of 13

    Variable Modify String: Append %T2% to %T3%

    Variable Modify String: Save %T3% to Environment Variable

    // Replace Environment variable "CRLF" in String T1 with space

    Replace "%CRLF%" with " " in %T1%

     

    I am trying to do this in an htm file. I'm not sure if that's the problem.

     

    Please help. Thanks.

  7. You're saying it doesn't recognize window titles? I know I have macros that use window titles on her machine and I'm pretty sure they work. I'll have to double check next time I'm in. Can you give me a specific example of how it's not working? IE is it as simple as a window title scope limitation?

     

    Well, what do you know? I called support in early May of 2008 with Version 3.7b. Support told me that they knew of the problem and were waiting for a compiler for Vista 64. I left a message a month later (I am an Macro Express addict so one month without ME is like a year for me), but no one responded to my post. Since then there was release 3.7c and 3.7d. None of the notes mentioned that ME was now Vista 64 compliant so I assumed that the problem was being ignored. Until, low and behold, you shed light on the topic for me. That's great!!! I can continue to use my favorite software again!!! Thanks a million!!!

     

    Alex

  8. How is it not compliant? I have it on several Vista machines and at least one user is 64b and I haven't had any complaints from her. But I am planning on rolling out more Vista 64b machines so I would like to know if something doesn't work. But you might look into AutoIT, I see it's 64b compliant now.
  9. Actually, I just found a bug. MacroExpress doesn't work with Excel 2007 in Vista 64 if a second Excel program is opened up. Excel allows you to open it up numerous times (i.e. not just new spreadsheets, but new instances of MS Excel itself). Is a second Excel is running, Macro Express won't launch.

×
×
  • Create New...