I don't know about others, but most of the integration work I've done that is the case. It's rarely the case that only 1 application uses the database and all the data follows a consistent set of conventions and good modeling practices. Not to dog VB or anything, but the legacy app is primarly a VB winforms app, which looks like a team of blind monkeys went to town.
On Sep 26, 6:34 pm, "Fabio Maulo" <[EMAIL PROTECTED]> wrote: > BTW have more than one application accessing the same DB without an > applicationServer or without using SOA is the right way to disasters (and > you are a witness of that). > > 2008/9/26 Peter Lin <[EMAIL PROTECTED]> > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
