HP3000-L Archives

September 1995, 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:
Bob Walker <[log in to unmask]>
Reply To:
Date:
Wed, 27 Sep 1995 09:47:37 PST8PDT
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
> From:          "<Elbert E Silbaugh>" <[log in to unmask]>
 
> I have a SQLDBE (environment) with several TurboIMAGE databases
> attached. All residing in the same GROUP.ACCOUNT.
>
> I also have a TI DB attached to the same environment but from a
> different account. One table in this case - called XYZ.
 
As someone else mentioned, a good check is from ISQL. If you can
read the data with ISQL, odds are the other method will work too.
 
It sounds like the logon user(from Access) is both DBA and Image
creator of the 'local' databases.
Your 'external' database creator must grant access to its tables to
the logon user.
This will require that you  put a lockwork on the 'external'
database and use ImageSQL: (Set dbe SQLDBE,
Set turbodb tidb.pub.external,lockward=????,
 'Add User mgr@external with pass=BLAHand mode=5')
 
Haven't done this for a while,, but syntax this should be close.
 
 
 
--=--=--
Bob Walker, Computer Centre  --  [log in to unmask]
Capilano College, North Vancouver, BC, CANADA.

ATOM RSS1 RSS2