Hi Peter,

I agree with your perceptions - and I suspect that most people's first 
encounters with DBMS tables produce the same concerns.  But this is a 
significantly different data environment from "normal" MapInfo TAB file use.  
The fact that MapInfo insists on using "Definition Table" TAB files as part of 
this environment perhaps masks this fact and escalates the nuisance factor.

SUGGESTIONS:
===============
1.  Create a "plain vanilla" user account, with read-only, non-sensitive access 
to your Oracle Spatial tables and views, then circulate this name and password 
for widespread use.  You could even go so far as to embed the "PWD=xxxx" string 
in the TAB file headers so that connection is totally automatic and your users 
will never be troubled by a login prompt again.  For example, create a 
user "GISDATA" with a password "GISDATA" in your Oracle database, then grant 
SELECT privileges to this user on all relevant spatial tables/views in other 
schemas.

2.  If you have the situation where different users have different security  
privileges (such as selective access to data controlled by the database) then 
you have no choice but to use individual logins.  However, in this case, you 
should *not* be leaving TAB files "lying around" for other users to open 
anyway.  If this is your situation, then you will need to manage the 
connection / disconnection / TAB file clean up programmatically.

It takes a bit of getting used to, but I think you will find that some 
combination of the above will provide the necessary blend of flexibility, 
functionality and security which you require.  I would be interested to hear if 
it does not.

Cheers,
David Jerrard

Quoting Peter Horsb�ll M�ller <[EMAIL PROTECTED]>:

> Hi,
>  
> Well, I'm still strugling with Oracle ;-)
>  
> When I open an Oracle table in MapInfo, and stores a tab file on disk, it
> look like this:
>  
> *************************
> !table
> !version 550
> !charset WindowsLatin1
> Definition Table
>   Type ODBC
> begin_metadata
> "\IsReadOnly" = "FALSE"
> "\DATALINK" = ""
> "\DATALINK\Query" = "Select * From CMIS.CMIS_PARCELS Where INSTR('ORG CURR',
> STATUS) > 0"
> "\DATALINK\ConnectionString" = "SRVR=tnt;UID=drs"
> "\DATALINK\ToolKit" = "ORAINET"
> "\CACHE" = "OFF"
> "\MBRSEARCH" = "ON"
> end_metadata
> ***********************
> The thing that bugs me is that it writes the uid into the file. I would have
> it using the availeble connection, because when a different user opens this
> table afterwards he is propted for the password for the user 'drs'. This new
> user of course could enter his own username/password, but he already has
> established a connection to Oracle, so I just want MapInfo to use this
> connection.
>  
> Any ideas how this can be established, or does every user just have to have
> their tables locally, in the temp folder for instance ?
>  
> TIA,
> Peter Horsb�ll M�ller
> GIS Developer
> Geographical Information & IT
>  
> COWI A/S
> Odensevej 95
> 5260 Odense S.
> Denmark
>  
> Tel   + 45 6311 4900
> Dir   +45 6311 4908
> Mob +45 5156 1045
> Fax  + 45 6311 4949
> E-mail [EMAIL PROTECTED]
> http://www.cowi.dk <http://www.cowi.dk/> 
> 




---------------------------------------------------------------------
List hosting provided by Directions Magazine | www.directionsmag.com |
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Message number: 14172

Reply via email to