HP3000-L Archives

October 1997, Week 1

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:
Robin Foley <[log in to unmask]>
Reply To:
Robin Foley <[log in to unmask]>
Date:
Thu, 2 Oct 1997 19:01:01 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (53 lines)
The issue of addressing specific data views is common to almost all ODBC
users. The best way of managing data views IS on the Server within the DBE.

<plug>
LINKWAY - The ODBC Driver for HP3000 - was launched in the US at HP World
'97 in Chicago last month. It provides inherent data dictionary facilities
which have frequently created user friendly views of data which in their
own right eliminated many of the needs for additional complex views, which
are also supported by LINKWAY.

The benefits which accrue from utilising data views within the DBE include
the ability to use the power of SQL to execute multi-table and multi-DBE
queries.
Security provision within LINKWAY includes no access, or read access or
read/write access by user by PC client application within approved DBE data
views and within the security wall provided by Security3000 from VESoft.

CSL, authors of LINKWAY, have been delivering secure, user friendly,
standards compliant ODBC Driver software for HP3000 users since 1994, (and
32-bit software since 1995) which has been providing solutions to major
HP3000 users not only in the area of data access but also in PC
Client/Server development utilising just about ALL known tools.

Current implementations include integration of live HP3000 data with the
www. Then you DO need to secure your data views!
<End of plug>


>At 09:56 AM 10/2/97 -0700, Backuj wrote:
>I am in the process of evaluating Minisoft's ODBC/32 and I have already
>evaluated MB Fosters ODBCLink.  The main reason I focused on these two is
>the ability to access my IMAGE databases with native calls.  The PC based
>tools I am using are Crystal Reports, Excel, Access, etc.  The problem I am
>having is the complexity of the IMAGE databases.  I would like to be able to
>create "views" of the data that pre-link the appropriate files and only show
>the needed fields.  Then when my "end user" uses their PC based tools they
>would use a appropriate "view" (a simplified view of the database).  I'm
>pretty sure I can do this if I defined a DBE layer for my IMAGE databases
>but I would rather not do that.  Does anybody know of another approach?
>Perhaps something at the PC level that would allow me to continue to access
>the databases natively?



Regards

Robin Foley
Computing Solutions Limited
Tel: +44 1905 794 400 (UK: 9.00 a.m. - 5.30 p.m.)
Tel: +44 860 409 473 (24 hrs)
Fax: +44 1905 794 464
E-mail: [log in to unmask]

ATOM RSS1 RSS2