> Our user group member was totally frustrated by his initial attempts to get > the damn thing working because no one ever mentioned to him that the older > ODBC driver wouldn't cut the mustard. He kept making the false assumption > that it was something that he was or wasn't doing from his efforts that was > causing the problem. A simple statement by MS to the fact that the old > driver didn't have a sonowball's chance in hell of working would have saved > him hours and hours of wasted time and frustration. Carl, the fact it was an ODBC problem was discussed in MS newsgroups (In the visual interdev newsgroup if I remember correctly) long before MS released the updated drivers it is true though (to my knowledge) there was nothing public/official from MS Arnon