Macro date and time update without a save

[Me_again]

Me_again, could you try opening a macro on the 14th or later that was opened on the 13th and see if it updates?

I opened/closed those same two macros a couple of times this AM (1/14) and the date did not change, they still show last modified 1/13.

[jpuziano]

Hi Marcus,

I posted this here instead of on the beta forum since this seems to be the same bug... it seems to have returned in 9.0.024 beta (and I think it was in 023 too). I re-read this 2 page forum post, saw a couple ideas on what may be causing this; was the cause ever nailed down? I think it was fixed in the last production release but unfortunately it seems to be back.

I'm running: Microsoft Windows XP Professional, Version 2002, Service Pack 1

Anybody else seeing this behavior out there?

Hi Support,

Same thing is happening for me too. I'm running 8.0 beta 007 on XP SP2.

- Fire up Macro Scheduler
- right click on systray icon, left click on Show
- right click on a macro last touched a month ago, left click on "Edit Script"
- just "look" at macro, nothing else, click "X" to close edit window
- now macro in main window shows today's date/time in "last modified" column

[Marcus Tettmar]

I just tried that and nothing changed. Unable to replicate following those steps.

[JRL]

I've continued having this problem all along with 8.0 and now with 9.0 but have resolved it by changing my ways.

I just tried opening a macro in macro properties, then opened the editor, then copied some text to the clipboard, then closed the editor and then OKd the macro properties dialog without making any changes. No change to the date. So it seems fine here, unless you're doing something different. Are these the steps you are taking?

Since I learned that the problem doesn't exist if you edit through the properties window, I just do that with old scripts I'm not editing.

Later,
Dick

[Marcus Tettmar]

I *wish* I could replicate this, but as long as I don't change the script, or save it, the modified date does NOT change. If I just LOOK at the script as suggested here and close or cancel, nothing happens.

[jpuziano]

I've continued having this problem all along with 8.0 and now with 9.0 but have resolved it by changing my ways.

Since I learned that the problem doesn't exist if you edit through the properties window, I just do that with old scripts I'm not editing.

Hi JRL,

Ahh so it didn't go away. Thanks for that workaround, I'll just use the properties window when looking at old code and only resort to the Advanced Editor when I know I'll be making changes.

I *wish* I could replicate this, but as long as I don't change the script, or save it, the modified date does NOT change. If I just LOOK at the script as suggested here and close or cancel, nothing happens.

I guess the trick is finding out where in the code it is happening. Pretty hard to do that when you can't replicate the problem. If you made a "debug version" of the beta that would log everything in great detail to a logfile, I'd be glad to install it on the home PC, perform this action and then send you the logfile... just let me know.

[jpuziano]

I updated Bug #69 - Last Modified Date change is back in BugTracker with the following:

Posted By: jpuziano
Date: 10:39 AM 11-12-2006
This bug also occurred for me in 9.0.024 beta though it is intermittent and cannot be reliably replicated AFAIK.
See forum post here: http://www.mjtnet.com/forum/viewtopic.php?t=1861

If anyone can come up with steps to repeatedly cause this bug to happen, please let Support know.

[JRL]

Jupuziano. I think you found it.

I have many old macros where the macros.dat entry for scheduled hours and minutes is 0:0 rather than 00:00. One entry for example:
0002 Order_Entry_Rebuild::00:00:0:0:1:0:"":0:::nn:nn:0::0:0:1::H:General\Infisy:I:N:::
Has a date and time 11/08/2003 4:34 PM. I'm going to open it in the editor by right clicking the name from the Macro Scheduler main menu, right clicking on edit. Now that its open, I'm closing it by selecting the "X" in the upper right corner. I have done nothing to the file so it closes with no warnings. The date and time is now 11/15/2006 8:53 AM. The macros.dat line for this macro now says:
0002 Order_Entry_Rebuild::00:00:0:0:1:0:"":0:::nn:nn:0::00:00:1::H:General\Infisy:I:N:::

If I exit completely out of Macro Scheduler, open the macros.dat file using Notepad, and alter the scheduled hours and minutes from 00:00 to 0:0 on a macro I was working on yesterday. Save the macros.dat file, reopen Macro Scheduler and open the macro using the right click menu and selecting edit then close it without making any changes. the date and time update to "now". And the scheduled hours and minutes are back to 00:00.

So the answer to this is to "fix" the entries in the macros.dat file by changing the scheduled hours and minutes from 0:0 to 00:00?




Later,
Dick

[Marcus Tettmar]

You guys are killing me!! The last modified date refers to the .SCP file. It gets the age of the .SCP file. It has absolutely nothing to do with anything in the macros.dat file. It refers to the last modified date of the .SCP FILE!

[JRL]

Sorry... don't mean to be mean. But I can reproduce this.... have you tried it?

[Marcus Tettmar]

Yes. And I can see the source code! I'll even show it to you if you like. It does one thing and one thing only, it retrieves the file date of the .scp file!

What is the file date/time of your .scp file in DOS?

[Marcus Tettmar]

You're confusing cause and effect here. You closed the editor, the file date was changed AND you noticed that the runtime was formatted to 00:00. Two effects. They both happened, yes, but it doesn't mean they are linked!

[JRL]

Looking at the date and time in DOS the two scp files I messed with are both updated dates and times.

Cause and effect? Action and reaction perhaps.

1) Exit from Macro scheduler.
2) Open macros.dat in DOS
3) alter the appropriate 00:00 to 0:0 for a given script
Order_Entry_Rebuild::00:00:0:0:1:0:"":0:::nn:nn:0::00:00:1::H:General\Infisy:I:N:::
Order_Entry_Rebuild::00:00:0:0:1:0:"":0:::nn:nn:0::0:0:1::H:General\Infisy:I:N:::
4) open Macro Scheduler
5) edit the chosen macro by using the right click menu
6) close the editor having done nothing
7) time and date is updated in the MAcro Scheduler main menu
8) time and date is updated in DOS

[Marcus Tettmar]

Now change any other field in macros.dat that gets modified by the program.

Same thing.

All you are doing is causing Macro Scheduler to have to save the macro again, because you are reinitializing the macro. It reformats the time field and therefore has to mark the script as changed and re save it.

[Marcus Tettmar]

The problem here is that by manually editing a value in macros.dat which the macro needs to change you are forcing it to save everything. This therefore modifies the last modified date. So it doesn't really prove anything.