[comp.databases] Allowing Users To Access Database From Another File System

aec@cbnewsd.att.com (arthur.e.cooper) (11/07/90)

This may be a trivial question, but it has me baffeled.

I've created a database and want to permit access from another file
system (on the same machine). The grant connect statement, in this
case, allows a user from the other file system to interact with the 
database tables to produce reports but not get into the mode to add 
records, query, or update.

This is the problem:

A typical user would logon to the given file system. A command in
the .profile executes a UNIX shell (run program) on the file system
that will directly access the database and its programs. The run
program sets the environment and executes another shell that displays
the main menu and prompts for input. 
After selecting, from the menu, the item that will call the function
sperform which executes the form specification file, the system prints
an X on the next line, there is a pause, the screen is cleared and the
menu is displayed again. What we should see at this point is the first
screen. This problem only exist when attempting indirect access.
I've used both grant all privileges and grant connect (with appropriate
revokes between the two) but the results remain the same.
If anyone would care to offer suggestions or possible solutions I'd
certainly appreciate the help.
-- 


    Art Cooper    AT&T Bell Laboratories    att!ihlpl!wd9aet   708-979-3049

aec@cbnewsd.att.com (arthur.e.cooper) (11/15/90)

> 
> This may be a trivial question, but it has me baffeled.
> 
> I've created a database and want to permit access from another file
> system (on the same machine). The grant connect statement, in this
> case, allows a user from the other file system to interact with the 
> database tables to produce reports but not get into the mode to add 
> records, query, or update.
> 
> This is the problem:

Problem description deleted.

My thanks to everyone who sent suggestions for solving what I thought
was an INFORMIX problem. Setting permissions on the termcap file to
allow read access to "other" (since we are executing from another file
system in the UNIX environment) solved the problem.
I've sent email to some but lost a couple of addresses. Did'nt want to
omit anyone.
-- 


    Art Cooper    AT&T Bell Laboratories    att!ihlpl!wd9aet   708-979-3049