QUOTE(dgionet @ Aug 24 2012, 04:05 PM)
Hi Mike,
I have reloaded the Canton template and have done some checking again. It has been a while since I have used it, so I will try to remember.
One thing you mention has been experienced in the past, related to the region 100 error. It did occur again this week.Again I can't figure it out since the 100 region number ( or others which may appear in similar messages) is present in the SWLTDBCantonLOCALS file. But this message appears only occasionally. It does the same with the YARDS template. When this happens, I usually exit the program and reload it and am able to load the template and create a SLG generated activity. I have been able to create activities this week with all four templates.
As to the paths mentioned (Interchange to Grove City or the other way) the SLG-generated act for the EB and WB uses the proper path direction.
In the package, there are one template for the EB and the WB. Each template has only one path and is set on the right direction. The other two are the LOCALS and the YARDS templates and they are the ones which generates occasionally this message.
I will try to look it again if I can find the issue which generates sometimes this message. But that shouldn't prevent the user to create successfully SLG acts.
Thanks for the reload, Denis, and for the quick response.
It does indeed seem to work every time if each run of the activity generator is from a cold start (as opposed to generating another activity in the same session). This suggests to me, a C/asm programmer, that the problem is not in the template but is somehow in AG4 itself, a failure to fully re-initialize all variables when a second or later run is made in the same session.
I say this because I was able to make it fail by trying to generate a local activity immediately after generating an eastbound activity in the same session. This time it reported region 82 as the error, not 100, suggesting that the region number that gets reported is somehow dependent on whatever data was generated in the previous run of the same AG4 session.
Anyway, it's obviously not a big deal if the user is aware in advance that the system should be used once only per session.
I did not bother to retest the original installation, which I destroyed in order to make room for the installation of your revised upload. Presumably it would have worked just as well if I had followed the use-once-only rule that you suggested.