Uniobjects.Net is the base requirement. MV.NET builds on this and gives you a heap more (tho infact you can use it without uniobjects.net)
So it depends if you want simple connectivity to the DB to do commands and subroutine calls, for which uniobject.net would suffice, or if you want any of the other fancy stuff on top that MV.NET will give you ... -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Perry Taylor Sent: 28 May 2013 00:45 To: U2-Users List Subject: [U2] [UV] UniObjects.Net vs Thrid-party Products I'm investigating the pros and cons to using UniObjects.Net vs third-party products such as MV.Net, etc. Anyone care to chime in with your experiences? Thanks. Perry Taylor Senior MV Architect ZirMed 888 West Market Street, Suite 400 Louisville, KY 40202 www.zirmed.com<http://www.zirmed.com/> CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. ZirMed, Inc. has strict policies regarding the content of e-mail communications, specifically Protected Health Information, any communications containing such material will be returned to the originating party with such advisement noted. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
