PH 7.10G on VMS 7.1.2 and Oracle

Thu, 12 Jul 2001 11:53:05 +0100

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C10AC0.D76151C4
Content-Type: text/plain; charset="iso-8859-1"

Various helpful people have commented further on my reply, but can I remind
you that it wasn't me that had the problem - I was just trying to help out
Mike by pointing out that PowerHouse 7.10.G did not support Oracle RDBMS (as
opposed to Oracle Rdb) databases so the "conversion" he was inquiring about
was not possible without upgrading to PowerHouse 8.x, which for 8.10 and
8.20 is a non-trivial exercise - changing the dictionary would be the least
of his worries! 8.30 is a better proposition for existing VMS systems but is
still not actually released.

We are running PowerHouse 7.10.G4 on Oracle Rdb 7.0.6.1 and have no
intention of converting to Oracle RDBMS!

Please reply to the List Server rather than directly, thanks.

Regards,

Kevin Gordon
Systems & Computer Services Department
Sea Containers Services Limited
London 

-----Original Message-----
From: Gordon,Kevin [mailto:Kevin.Gordon@seacontainers.com]
Sent: Thursday 12 July 2001 10:32
To: 'Powerhouse List'
Subject: RE: PH 7.10G on VMS 7.1.2 and Oracle

At the risk of being overly simplistic, I thought PowerHouse 7.10.x didn't
even support true Oracle databases, so you'd have to upgrade to version
8.something, with all that that entails, in any case.

Regards, 

Kevin Gordon 
Systems & Computer Services Department 
Sea Containers Services Limited 
London 

-----Original Message----- 
From: Lamers Mike [ mailto:Mike.Lamers@phs.com <mailto:Mike.Lamers@phs.com>
] 
Sent: Tuesday 10 July 2001 19:37 
To: 'Powerhouse List' 
Subject: PH 7.10G on VMS 7.1.2 and Oracle 

Hello ... 
We currently run PH 7.10G on VMS 7.1.2 with an Oracle/RDB database 
(V7.0-16). 
We are considering converting the database from Oracle/RDB to "true" Oracle 
7.3.3.6 (or higher). 

Does anyone know if we would have to do anything special with any of our 
Powerhouse code?  Would the dictionary be affected?  Would we need to 
recompile all Quick screens?  Any other issues to consider? 

Thanks 

Mike Lamers 
PacifiCare of Colorado 
Health Care Economics (CO82-214) 
(719) 522 - 6758 
mike.lamers@phs.com 

******************************************************************************
The information contained in this e-mail is confidential. 
It may also be protected by legal privilege. 
It is intended only for the stated addressee(s). 
If you are not an addressee you must not disclose, copy, circulate nor use the information contained in it. 
If you have received this e-mail in error please inform the sender immediately and delete it and any copies from your system.
******************************************************************************

------_=_NextPart_001_01C10AC0.D76151C4
Content-Type: text/html; charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: PH 7.10G on VMS 7.1.2 and Oracle</TITLE>

<META content="MSHTML 5.50.4616.200" name=GENERATOR></HEAD>
<BODY>
<DIV>Various helpful people have commented further on my 
reply, but can I remind you that it wasn't me that had the problem - I was just 
trying to help out Mike by pointing out that PowerHouse 7.10.G did not support 
Oracle RDBMS (as opposed to Oracle Rdb) databases so the "conversion" he was 
inquiring about was not possible without upgrading to PowerHouse 8.x, which for 
8.10 and 8.20 is a non-trivial exercise - changing the dictionary would be the 
least of his worries! 8.30 is a better proposition for existing VMS systems but 
is still not actually released.</DIV>
<DIV>&nbsp;</DIV>
<DIV>We are running PowerHouse 7.10.G4 on Oracle Rdb 7.0.6.1 
and have no intention of converting to Oracle RDBMS!</DIV>
<DIV>&nbsp;</DIV>
<DIV>Please reply to the List Server rather than directly, 
thanks.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Regards,</DIV>
<DIV>&nbsp;</DIV>
<DIV>Kevin Gordon Systems &amp; Computer 
Services Department Sea Containers Services Limited London </DIV>
<DIV>&nbsp;</DIV>
<BLOCKQUOTE>
 <DIV class=OutlookMessageHeader>-----Original Message----- From: Gordon,Kevin 
 [mailto:Kevin.Gordon@seacontainers.com] Sent: Thursday 12 July 2001 
 10:32 To: 'Powerhouse List' Subject: RE: PH 7.10G on VMS 
 7.1.2 and Oracle </DIV>
 At the risk of being overly simplistic, I thought PowerHouse 
 7.10.x didn't even support true Oracle databases, so you'd have to upgrade to 
 version 8.something, with all that that entails, in any case.
 Regards, 
 Kevin Gordon Systems &amp; Computer 
 Services Department Sea Containers Services 
 Limited London 
 -----Original Message----- From: 
 Lamers Mike [<A 
 href="mailto:Mike.Lamers@phs.com">mailto:Mike.Lamers@phs.com</A>] 
 Sent: Tuesday 10 July 2001 19:37 To: 
 'Powerhouse List' Subject: PH 7.10G on VMS 7.1.2 and 
 Oracle 
 Hello ... We currently run PH 7.10G on 
 VMS 7.1.2 with an Oracle/RDB database (V7.0-16). We are considering converting the 
 database from Oracle/RDB to "true" Oracle 7.3.3.6 (or 
 higher). 
 Does anyone know if we would have to do anything special with 
 any of our Powerhouse code?&nbsp; Would the dictionary 
 be affected?&nbsp; Would we need to recompile all 
 Quick screens?&nbsp; Any other issues to consider? 
 Thanks 
 Mike Lamers PacifiCare of Colorado 
 Health Care Economics (CO82-214) (719) 522 - 6758 mike.lamers@phs.com 
 <CODE></BLOCKQUOTE></CODE><CODE> 
 
****************************************************************************** 
The information contained in this e-mail is confidential. 
It may also be protected by legal privilege. 
It is intended only for the stated addressee(s). 
If you are not an addressee you must not disclose, copy, circulate nor use the information contained in it. 
If you have received this e-mail in error please inform the sender immediately and delete it and any copies from your system. 
****************************************************************************** 
</CODE></BODY></HTML>

------_=_NextPart_001_01C10AC0.D76151C4--