|
When I get a parse error on a schedule file, I like to import small sections of the file at a time to localize the error. Of course you first back up the original file, then take the original file and import, say, just the first 40 days of the schedule. If you don’t get an error, then you know the problem isn’t in the first forty days. Then I’ll import days 41-80, and if I get an error, I know the problem is in days 41-80. So then I’ll try to pinpoint further. I’ll import days 41-50, and if I get an error there, I know the problem will be in those ten days. Usually by the time I pinpoint the error to ten days, that’s simple enough where I can spot the missing /> or the extra quotation mark. Once I find the error in day 44, for example, I go back to my full backup schedule, correct day 44, then the schedule should import correctly.
|