Skipping #1.

#2 All ODBC access is Read Only here.
It is set globally in the MSJOB,MGR.MINISOFT,MM job.

#3 Anyone who has access to the system can use ODBC,
provided they have the Client side.

#4 If a users already has Minisoft's ODBC installed,
all I do is e-mail the latest 3kodbc.dll and tell them
to put it in their C:?Windows?System? subdirectory.
I then wait for a time when no one is accessing the
ODBCSRVR.MM.MINISOFT kill the MSJOB, and upload
the host file.*  (If users start complaining it their
ODBC doesn't work, I ask them if they replaced the
.dll I sent them.  This usually does the trick.
Although there was one time when their latest ODBC
was out of whack with Omnidex's TPI, and it took
Minisoft a few days to figure it out.**)

* I think the latest iterations replace the file
without killing the MSJOB.

**  There's something ODBC doesn't like about
array fields in Turbo/Image, it has something to do
with "subscripted arrays" which is not a SQL standard,
(I think.)

Tracy M. Johnson
TRW Automotive Electronics
Sensors & Components

-----Original Message-----
From: Chip Dorman [mailto:[log in to unmask]]
Sent: Tuesday, March 28, 2000 9:48 AM
To: [log in to unmask]
Subject: ODBC rollout guidance needed


Hi y'all,

We have tested and now purchased MiniSoft's ODBC driver and
will soon be ready to begin the roll-out.  I am concerned that there
is a possibility for this implementation to get out-of-hand if we don't
setup some guidelines and standards for it use.  Those of you who have
implemented ODBC connections to your Image databases, would you
share some of your standards and guidelines with me.  War stories
would be appreciated, too.

Specifically...
1) What are the naming conventions you use for "cfg" files and schema files?

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?

3) How are you handling overall security for ODBC?

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

Any guidance, observations and general pearls of wisdom will be greatly
appreciated.

TIA,
Chip Dorman
Greenfield Industries/KMT
Augusta, GA