The pioneers of this planning planet have resolved my problem at that time with the same explanations as Ronald Winter.
Now I see this, all we are having the same problems at different times.
But it is so strange to face such a problem although we believe that P3 is quite good software. I could not accept such a problem after paying ???? USD to that software.
Member for
20 years
Member for20 years
Submitted by Marcio Sampaio on Wed, 2006-03-08 08:33
P3 (being an 16-bit software) was written when directories were not nested. It so happens that P3 cannot work on schedules that have more that 64 characters in the fill name (directory + file name.) Sometimes, your administrator may set-up a disk alias that substitutes a long directory string as a virtual disk drive. This lets you run schedules in very nested directories. Sometimes F9 does not use the virtual directory name and generates this error.
Do you understand the problem now? The easy answer is to remove some of the nested directories. Good luck!
Member for
20 years
Member for20 years
Submitted by Marcio Sampaio on Tue, 2006-03-07 12:31
Member for
20 yearsRE: (F9) - P3
??
Member for
21 yearsRE: (F9) - P3
Dear All,
I had already faced that problem for a while ago.
The pioneers of this planning planet have resolved my problem at that time with the same explanations as Ronald Winter.
Now I see this, all we are having the same problems at different times.
But it is so strange to face such a problem although we believe that P3 is quite good software. I could not accept such a problem after paying ???? USD to that software.
Member for
20 yearsRE: (F9) - P3
Thanks Ronald,
Very good your explanation. Now I understood perfectly the reasons that had generated the error.
Kind regards,
Marcio Eduardo
Rio de Janeiro - Brazil
Member for
22 years 10 monthsRE: (F9) - P3
More of the same.
P3 (being an 16-bit software) was written when directories were not nested. It so happens that P3 cannot work on schedules that have more that 64 characters in the fill name (directory + file name.) Sometimes, your administrator may set-up a disk alias that substitutes a long directory string as a virtual disk drive. This lets you run schedules in very nested directories. Sometimes F9 does not use the virtual directory name and generates this error.
Do you understand the problem now? The easy answer is to remove some of the nested directories. Good luck!
Member for
20 yearsRE: (F9) - P3
I got it.
This error messages happens when the
folder where the schedule files are located is very
"deep" in the subfolders structure. For example, when
the P3 files are in a folder like
C:\Folder\subfolder1\subfolder2\subfolder3\subfolder4\.....\
I moved the files to a "shallower" folder the
message is not generated by P3.
Sorry ... very simple.
Thanks.
Member for
20 yearsRE: (F9) - P3
And how can I resolve it?