Charlotte Foust
charlotte.foust at gmail.com
Mon Jan 23 16:10:56 CST 2012
Mark, If they have nothing after 2 years, then they should litigate. They should at least have had a working interface to replace the basic Access GUI within months and the enhancements to totally replace the functionality should have been down well within 2 years . The capability is all there in .Net, although it's easier to achieve if you work with some of the 3rd party controls and report builders rather than rolling your own in the native Visual Studio environment. Many of the 3rd party tools actually allow you to import from Access, although you have to do a lot of work after the fact to clean them up and the code doesn't work, of course. Never do it with a form, but it can be useful for simple reports. Sounds like someone was using the project for OJT and couldn't actually deliver. Charlotte Foust On Mon, Jan 23, 2012 at 12:16 PM, Mark Simms <marksimms at verizon.net> wrote: > Ah yes John...and that's the "big problem"....and this is likely the reason > my former client is moving towards litigation with the developer in their > Access to DotNet migration and upgrade. It's been over 2 years now, and > they > still have....nothing. > > > Whereupon the kitchen sink is there by demand and you are not given the > > option. ;) > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > > > Website: http://www.databaseadvisors.com > > >