RE: VB, ODBC and AS/400

[Pete Hall <peteh@xxxxxxxxxx>]

At 09:55 PM 2/2/98 -0800, John Earl wrote:
>I'm still not sure how you would do that, even with exit programs.  How can
>an exit program tell the difference between, say a VB ODBC update and an
>Excel ODBC update?  From the perspective of a sysadmin, the VB update might
>be okay (because it's a homegrown app with all the apporpriate edits in
>place) and the Excel update would never be okay (No edits, no field
>integrity, etc.).  But to the exit program, they're both just ODBC updates, no?

Well, what I've done is to put a table allowed commands in the program. If the 
statement is one that can change the database, I look at the table to see if 
the command is registered. If it isn't, I don't allow it. I also don't allow 
CALLs to QCMDEXC, but calls to any other program, at least currently, are 
allowed. That part is probably not foolproof, but so far has been sufficient.

Pete


Pete Hall
peteh@inwave.com 
http://www.inwave.com/~peteh/

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---