Importing Macro(s)

[iceman]

In some future version, please consider making it possible to retain the imported macro's original Modified date and time stamp in the destination/"Importee" macro.

 

Thank you.

[lemming]

Yes, that would be useful.

 

I sometimes shuttle macros between work and home, and I have a hard time keeping track of which have been modified.

 

Right now, any imported macros are set to the current system time/date.

[iceman]

Here's a potential work around that just came to mind this morning: put a date stamp in the macro's Nickname (e.g. PutData20060413).

 

The following is how I am going to implement the prior:

Today, I wanted to change my PutData macro, which I have in multiple macros. So I created a copy of it, made changes, and renamed it to PutData20060413. Then I deleted all the existing code in PutData and added one line of code, Macro Run: PutData20060413. I don't have to change any of the other macros that Macro Run: PutData. I can and will import the two macros into the other macros that now have an outdated PutData macro. Cool!

 

Now, I can also create different test versions (e.g. PutData20060418TEST) and upgrade (e.g. PutData20060420) by just changing the single reference in PutData, and not have to dig in all of the other macros that reference the original PutData.

[kevin]

Your suggestion has been added to our tracking system. You will receive an email confirmation containing the tracking number assigned to your request.

 

To request a feature visit: http://www.macros.com/requestfeature.htm.