I just upgraded to SP1 for version 2009 and the batch COGO file does not seem to be capturing all the COGO routines. I see the traverse bearing and the curve routines, but the intersection routines are not being captured. Is there something I am missing in a setup?

We are not aware of any issues with Batch COGO, but if you can give us a series of keystrokes that you can get to not work correctly, please do. This way we can examine this and if it is a bug, try and get it fixed ASAP for the next version.

Sorry - my last comment was made by me without confirming with my head office. I had been out on the road for a bit, running a training course, and was not aware of this. My head office is well aware of it and have it documented in our bug tracking software.

From what I understand, this may be related to alpha-numeric point numbers vs. numeric point numbers.

Either way - the programmers are aware of this and it will be fixed as soon as they are able, and added to the version released at that time.

I haven't seen a problem with cogo entry not being recorded into the Batch file - and in testing this today i am not seeing this issue.

Exactly what cogo entry is not being captured into the batch file? Please provide a step-by-step set of instructions to reproduce this problem. If we can reproduce it, we can probably fix it.

The issue Glen mentioned, is that playing back a batch cogo file containing distance-distance intersections with alphanumeric points will not work properly. But in this case, the cogo entry is captured into the batch file, it is only playing it back that doesn't work unless you change the alphanumeric point ids to numeric ids.

Sorry it has taken so long to get back to you. To answer your request, all intersection commands in COGO are not being captured in the batch file routine. Only the traverse and curve functions are being captured. I do not use alpha-numeric point identifiers, kind of old fashioned about that, so that is not the problem. I was not having the issue until I loaded SP1 a couple of weeks ago.

OK I see what is happening now. Yes, this only affects the latest 2009 service pack, and for some reason I had a prior version installed when i tested this last week. We are currently beta testing MicroSurvey CAD 2010, so I will see if we can squeeze in this fix prior to release.