HP3000-L Archives

March 2000, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Peter Chong <[log in to unmask]>
Reply To:
Peter Chong <[log in to unmask]>
Date:
Tue, 28 Mar 2000 08:48:04 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
>>> Chip Dorman <[log in to unmask]> 03/28/00 06:58AM >>>

Specifically...
1) What are the naming conventions you use for "cfg" files and schema files?
I start with SQL@ ...

2) How to control user access through ODBC to your databases?  Do you
    have specific read-only/write-only ODBC users setup for your applications?

I believe the Minisoft ODBC/32 uses a Read/Write privilege on IMAGE, you specifies on DBSCHEMA..., not like IMAGE/SQL, but most of access control
you could write on your applications(VBA) base on security data set.
Like User/Form/Report matrix.
 
3) How are you handling overall security for ODBC?
The ODBC is just tool, It just connect MS WINDOWS to HP3000.

May be different connection for different security, I have one Access/VBA
connects many different IMAGE Data Base / Quiz Subfiles, but depending upon
user privilege they do not have all the ODBC connections.

4) How do you control ODBC driver updates?  Seems that the minisoft driver
    checks for version matches between the client and the server.

That is issues, I found out it is not downward compatible like HP3000 ;-)

ATOM RSS1 RSS2