Originally Posted by
Wally Bird
It's a simple logic-tree piece of code. Unless some human being simply pores over old itineraries then some piece of code somewhere picked it up post facto.
Now I am prepared to concede that the booking engine code is so complicated in a dogs-dinner kind of way that it's simply too much trouble to reprogram it to detect nesting at source. That's a long way from being impossible; impractical perhaps given the apparent competence of AC's IT department.
Yes Wally and while I said
impossible I should've instead used
impactical and cost prohibitive as IMHO it would be far too much IT trouble to catch relatively few nested tickets.
Again, AC can't even get a new workable res. program as seen in the whole Polaris debacle so expecting it to adopt one with this kind of technology is unrealistic IMHO.