The itinerary ID's are too complicated, too long and have no chronological relevance. ie, if a recent itinerary number is 1408 and I produce approx 100 itineraries a year, I then know that itinerary number 1308 would have been produced roughly 1 year prior. Would be good to be able to carry on from the itinerary ID's I am using in .net. This would make the transition much easier and gives the client less chance of making a mistake with the randomly generated itnerary ID's such as 5BA8 7D34. The next itinerary I produced in our system was then coded as DEB2 80A6!! - There's no logic to this progression.