Odd error in PH 840d

brian_matthewsbrian matthews brian_matthews_bmw@hotmail.com
Fri, 17 Dec 2004 00:19:10 +0000


Hi all,

I recieved some off-line feedback to this subject - and as one respondent is 
happy for me to send this to the list - I wiil assume the other is of like 
mind ( if not - don't reply to me offline :) )

( the following comment will become clearer further down - I suspect that 
files are assumed to be open share if not specified )

Reply 1

with OpenVMS and Oracle RDB we have "open read share" and no error; the view 
is a multi-table view (primary file), but still fairly simple. Another 
method that got rid of the error was to put activities find on the screen 
statement (ie: no entry allowed) and put DISPLAY on each field statement.

We've never had to do anything like this to view references in the past, 
with PH v710x or v830x, but 8.4 seems to be different from the others.

Another screen references a view that is a multi-table view, but all the 
fields on the screen are temps, and do not directly reference the view.  
This screen compiles and runs just fine.

Reply 1 end

Reply 2


I've reviewed our code that uses database views and found that in the 
majority of the cases our screens are set up with activity FIND (view only 
screens) or the files are often designer or reference files.

Out of the 262 view files, only 20 use the OPEN READ verbs. SHARE does not 
appear.

I did manage to find one screen where we use a multi-table view as the 
primary file. But we've place OPEN READ on the file.

In another case we have a single-table view as a secondary file. This view 
simply fetches what we consider current records in the table. In the screen 
we do a PUT on that file with no ill effects.

>From our short discussion, I'm not surprised Harold needed the OPEN READ 
SHARE on the file. It is a multi-table view and Oracle does not allow code 
to write to those files. For some reason PH is not catching that fact until 
he runs the screen. Alternatively changing the screen to a FIND only screen 
likely resolves the issue because PH will inactivate the update routines to 
confuse it self, and open the files read only.

Anyway, the real mystery is why the error appeared during a find. The only 
thing I can think of is that PH is trying to open the file for writing. As I 
said above, Oracle doesn't like that for multi-table views. So Oracle is 
returning the bad news to PH.

Reply 2 end

Bri,


>From: "Johnson, Harold A EDUC:EX" <Harold.A.Johnson@gems1.gov.bc.ca>
>To: "'brian_matthewsbrian matthews'" <brian_matthews_bmw@hotmail.com>,   
>powerh-l@lists.sowder.com
>Subject: RE: Odd error in PH 840d
>Date: Thu, 16 Dec 2004 11:11:04 -0800
>
>That was it!  Simply a change in the behaviour between versions.
>
>thnx!
>
>
>
>-----Original Message-----
>From: powerh-l-admin@lists.sowder.com
>[mailto:powerh-l-admin@lists.sowder.com]On Behalf Of brian_matthewsbrian
>matthews
>Sent: 2004 December 16 11:05 AM
>To: Johnson, Harold A EDUC:EX; powerh-l@lists.sowder.com
>Subject: RE: Odd error in PH 840d
>
>
>you might need to add 'open read share' to the file statement. I think I
>read that this is required for views in Quick.
>
> >From: "Johnson, Harold A EDUC:EX" <Harold.A.Johnson@gems1.gov.bc.ca>
> >To: powerh-l@lists.sowder.com
> >Subject: Odd error in PH 840d
> >Date: Thu, 16 Dec 2004 10:07:41 -0800
> >
> >Hi all.  We are getting an odd error when running PH 840c or 840d.
> >
> >"Missing message 1328   (TABLE_NAME_VIEW*01)"
> >
> >Simple code in qdesign.  Compiles fine, but when retrieving a SIN via the
> >SIN, gets the error.
> >
> >---------
> >screen test
> >file TABLE_NAME_VIEW in database primary
> >    access via sin using sin request sin
> >
> >
> >
> >field sin
> >
> >field first_name
> >
> >field last_name
> >
> >---------
> >
> >
> >Anyone know what this is?
> >
> >thnx
> >
> >
> >
> >= = = = = = = = = = = = = = = = = = = = = = = = = = = =
> >Mailing list: powerh-l@lists.sowder.com
> >Subscribe: "subscribe" in message body to 
>powerh-l-request@lists.sowder.com
> >Unsubscribe: "unsubscribe <password>" in message body to
> >powerh-l-request@lists.sowder.com
> >http://lists.sowder.com/mailman/listinfo/powerh-l
> >This list is closed, thus to post to the list you must be a subscriber.
>
>_________________________________________________________________
>It's fast, it's easy and it's free. Get MSN Messenger today!
>http://www.msn.co.uk/messenger
>
>= = = = = = = = = = = = = = = = = = = = = = = = = = = =
>Mailing list: powerh-l@lists.sowder.com
>Subscribe: "subscribe" in message body to powerh-l-request@lists.sowder.com
>Unsubscribe: "unsubscribe <password>" in message body to
>powerh-l-request@lists.sowder.com
>http://lists.sowder.com/mailman/listinfo/powerh-l
>This list is closed, thus to post to the list you must be a subscriber.
>= = = = = = = = = = = = = = = = = = = = = = = = = = = =
>Mailing list: powerh-l@lists.sowder.com
>Subscribe: "subscribe" in message body to powerh-l-request@lists.sowder.com
>Unsubscribe: "unsubscribe <password>" in message body to 
>powerh-l-request@lists.sowder.com
>http://lists.sowder.com/mailman/listinfo/powerh-l
>This list is closed, thus to post to the list you must be a subscriber.

_________________________________________________________________
Express yourself with cool new emoticons http://www.msn.co.uk/specials/myemo