At 09:47 AM 5/19/2004, KevinJ Jones wrote: ><snip> >The big move now is to take the existing app and merge it with Oracle, SQL >or leave it in Unidata. The R18 release will allow the users to choose >which database they wish. The code will stay in envision and talk via a >middle level translator which passes instructions out to the selected db. >We have been a Beta for the Oracle instance and it seems to work ok >(meaning no more bugs than you would suspect for any other Enterprise app.) ></snip>
[I've been working with Datatel's Colleague/Benefactor products about 5 years now.] Some time ago Datatel decided they could fix it so their Envision tool could support both Unidata and Oracle. Up to version R13, Envision and the design of their Unidata files etc. appear to be headed in a good direction. Envision clearly was designed to work on a MV database. There was potential for it to become a nice tool. The current R17 version we work on bears the scars from the impedance mismatch. More then once I've had some of their older tech's admit that the problem I was investigating with their help was a results of having to design the Unidata side in a manor that would leave folks on this forum scratching their heads, yet with out the change it would not work for the Oracle users. I find that Envision as it exists today adds a lot of unnecessary complexity to the mix. Both the Unidata and the Oracle versions have suffered. At present Datatel's Envision development tool does require some Unidata be present for those clients that chose the Oracle version. Datatel has chosen to head down the Web Services/XML route. They are working to separate Envision into layers of business rules/logic, User interface, and the chosen database back end. Envision relies on a strange extension of Pick Basic. I believe they'll use it to provide the business logic. This will include some XML based facility to interpret/communicate with the database and the UI. Unfortunately they will continue to rely on Wintegrate for the UI. XML/Web Services just might make the above separations work. >I have a question about his. If the Envision tool kit is written in >Universe, and the database will be Oracle, how will the Envision >programs work? Won't you still need to have a Universe license to >retrieve the Envision data? > >Frankly the Datatel interface and the bad taste it leaves in college >students mouths is one of Oracles strongest marketing ploys. > >No more bugs than any other Enterprise app? Datatel has to release >hundreds of patches a year. At least 3 a week. and they expect you to >test them before you install them. And will not support you unless you >are fully patched. Bear in mind the term "patch" applies not only to bug fixes, but also to system enhancements, and regulatory related changes (such as INS/SEVIS changes). >If Datatel is the flagship for U2, we deserve to be sunk. The current incarnation of Colleague is indeed a poor example of what can be done with MV databases. On the other hand, because it we are using Unidata, I find it relatively easy to create ways around the short comings. >Kevin Jones >(315) 445-4270 > > >>> [EMAIL PROTECTED] 5/19/2004 8:36:12 AM >>> ><"...but still, aren't there any mv-type systems that can bring this >"<guarantee" to the table?" >------- >u2-users mailing list >[EMAIL PROTECTED] >http://www.u2ug.org/listinfo/u2-users *-----------------------------------------------------------* Jon Wells Database Administrator Beloit College Information Services & Resources Beloit, Wisconsin 608-363-2290 [EMAIL PROTECTED] 608-363-2100 (fax) *-----------------------------------------------------------* ------- u2-users mailing list [EMAIL PROTECTED] http://www.u2ug.org/listinfo/u2-users
