blinder@oracle.uucp (Ben Linder) (12/12/88)
David Edwards of Kuwait Petroleum, Sweden writes: >Sounds interesting. We use oracle with PRO-C interface for the batch >programs, and sqlforms for screens. I don't know anything about >hypercard from a technical point of view. >Can you elaborate on what the object-oriented approach brings to >oracle specifically? Can you avoid using sqlforms, for example by >using hypercard instead? How compact is the code incomparison to C? >Are there things that are hard to do in C that are easy in hypercard >in connection with database applications? First, let me leave off technical discussion of HYPERCARD, and suggest COMP.SYS.MAC.HYPERCARD. Functionally, Hypercard stacks contain facilities for procedural triggers (language is HYPERTALK), much like SQL*FORMS. HYPER*SQL, which is a hypercard XCMD (external command) Oracle provides lets you embed SQL in Hypertalk just like C or COBOL. Looking at hypercard as a replacement to SQLFORMS does not do justice to it. SURE, you can simulate everything a sqlforms application does in hypercard, but there is lots more. One of the deficiencies of hypercard is that it has the potential for intuitively linking and presenting massive amounts of data, but lacks efficient data storage and portability. That is what Hyper*sql provides. As far as PRO*C, it works on the Mac just like anywhere else, so you can redo your screens in hypercard and keep your C programs. Code size is very hard to judge. If you tried to do all of the screen and presentation handling of hypercard on your own, your code will probably end up pretty large. If anyone out there has experience with database application on hypercard, please jump in. -Ben -------------------------------------------------------------------------- Ben Linder RANDOMIZE Oracle Corp Advanced Tech Consulting arpa: blinder%oracle@hplabs.hp.com uucp: ...hplabs!oracle!blinder ____________________________________________________________________ Ben Linder RANDOMIZE Oracle Corp