Mark Simms
marksimms at verizon.net
Mon Jan 3 18:33:39 CST 2011
Yes Jim, I concur. But at the same time blame squarely lies with Microsoft here. Poor job done on providing a web migration path that is robust and programmable. It could be done. They just elected not to do it. > Hi Shamil: > > I think the main reason for the issues with the major migration to .Net > is > that many here have hundreds of thousands of field-tested lines of code > tied > up in VB/Access and now have to throw out about twenty years of work, > to > start again from scratch.