From: Rev Dr Phil Herring Newsgroups: comp.databases.oracle,comp.sys.mac.hypercard Subject: Re: Oracle7 & Hypercard ??? Date: 10 Oct 1994 03:19:35 GMT Organization: Church of the Sacred Dial Tone Lines: 26 Distribution: world Message-ID: <37abs7$oah@wabbit.cc.uow.edu.au> References: <36ut19$gma@tycho.gartner.com> NNTP-Posting-Host: bastardo.cc.uow.edu.au X-UserAgent: Version 1.1.3 X-XXMessage-ID: X-XXDate: Mon, 10 Oct 94 13:12:53 GMT In article <3714v7$8h9@dcsun4.us.oracle.com> Doug Bitting, dbitting@us.oracle.com writes: >The Oracle Access drivers which are used to created the execsql XCMD are >designed for Oracle 6. They do not know how to handle the new Oracle7 >datatypes, they do not know how to call stored procedures, etc. Um, far be it from me to hassle an employee of the Big O, but we've been using the old Oracle Access stuff with O7 with no compatability problems. You *can* call stored procedures, and yes, some of the new datatypes aren't handled, but the the execsql XCMD didn't do such a good job on the V6 datatypes, either! Our transition from a V6 server to O7 was flawless. I'd like to know which SQL statements in the original poster's HC application don't work. The only problems that I can think of relate to different DD views (usually cured by running the appropriate scripts on the server) or datatype problems such as using CHAR instead of VARCHAR2. The execsql XCMD, of itself, should not present any problems, unless the database has changed. -- Phil. ------------------------------------------------------------------------- (c) 1994 Rev. Dr. Phil Herring revdoc@wumpus.cc.uow.edu.au - Church of the Sacred Dial Tone, Wollongong, Australia - Unauthorised reproduction of this article for profit will result in civil action. -------------------------------------------------------------------------