× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: VB, ODBC and AS/400
  • From: John Earl <johnearl@xxxxxxxxxx>
  • Date: Mon, 2 Feb 1998 21:55:49 -0800

Pete,

At 08:42 PM 2/2/98 -0600, you wrote:
>At 07:40 AM 2/2/98 -0500, David Knittle wrote:
>>One major gotcha with odbc, I think. Once you give users access to odbc on 
>>the 400, don't expect them to use it only with the vb programs you have 
>>written. They will use it in excel, access ( a real problem, as it provides 
>>an easy way for a user to update data in a non-controlled way), etc.
>
>That's very true, but easily fixed with an exit program. Not a major
project if all you need is to prevent updating. It get's a little dicier if
you need to allow SOME updates, but it still is not too bad.

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?

jte

+---
| 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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.