I created three macro files on my computer and they work good.  But when i copied them to another computer i get a message that says the file failed to open.  both machines are windows XP PRO with SP2.  Sesame is 1.1.4 The macros are in the path and folder as original machine.  Spelling has been triple checked, and path in the message matches the correct folder location.  Files have been changed to/from Read Only.  The originals are ReadOnly to prevent changes.   Only one person uses the computer and has full permissions.  files in that folder can be added/deleted/modified so it does not appear to be permissions.  Files were originally sent be email and thought they were damaged to they were all deleted.  Then the files were transferred directly using Symantec pcanywhere.  Why would the files fail to open?

thank you in advance for helping me

this is a standalone but why does that make a difference?  The full path is included when calling the macro?  But you did make me think about the pathagain.  This is the program line to call the macro:
@Macro("..\Utilities\Personal\Macros\Macrofile001.mac") but I just checked the other computer and the working directory is C:\Sesame\ on that one and is C:\Sesame\Programs\ on my computer.  So the real path is not being found.  I am going to change the program to include the real full path like this:
@Macro("C:\Sesame\Utilities\Personal\Macros\Macrofile001.mac").

I do think that will work now but sticll want to know why it makes a diffeerence as standalone or Client Server?  Same problem, possible wrong path?

I was right when I said I thought changing to the full path would work.  The macros are now running good.  And thank you for exsplaining about the server and the standalone differences.  But now i do not need to make sure that all users always have same path but must put the macros in the same place.  It seems that if i have network users i could put the macro files on the server.  but if they are on the server drive C and I use full path then macro files will not be found again?  Or will that be fixed if i start to use Server/Client instead of standalones?