Xref: alice comp.databases.oracle.misc:38875
Message-ID: <37BAD858.6691BE10@dced.state.ak.us>
Date: Wed, 18 Aug 1999 07:59:20 -0800
From: Calvin Crumrine <Calvin_Crumrine@dced.state.ak.us>
Organization: Alaska Division of Investments
X-Mailer: Mozilla 4.07 [en] (Win98; I)
MIME-Version: 1.0
Newsgroups: comp.databases.oracle.misc
Subject: Re: Why use pro*C
References: <7pdnd2$p55$5@news.vsnl.net.in>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: 18 Aug 1999 07:56:31 -0900, 146.63.104.9
Lines: 17
Path: alice!news-feed.fnsi.net!feed.newsfeeds.com!newsfeeds.com!newsfeed.mathworks.com!howland.erols.net!newsfeed.cwix.com!208.138.129.21!news.gci.net!146.63.104.9

I use Pro*C, Pro*COBOL, or Visual Basic when I want more control over how a user
accesses a database than triggers allow. It might be a canned report where the user
simply runs the program and enters the user ID/password or it might be data entry
where the user enters everything first then sends it to the database in a batch. It
might be for edit checks that are difficult or impossible in PL/SQL, for a more
user-friendly interface, or simply for more consistency in programming. (Note the
multiple languages above. I'm the only programmer in our shop who knows all 3
languages.)

Vasanth wrote:
> 
> Hi! folks
> 
> when do you use pro*c
> 
> Regards
> Vasanth