QTP update error
Latimer, Richard
richard.latimer@airways.co.nz
Tue, 16 Oct 2001 08:07:52 +1300
Hi George,
I have never tried this but it certainly sounds an interesting idea !
Brainstorming it with other people here our conclusion is that if it is an
occasional thing there is probably no solution.
However if you have the time and tools it is fairly straightforward to
declare the file in the PH Dictionary, either your usual one or you could
create a special one just for the job. Create or modify the dictionary using
PDL and then compile it but don't create the file in PHDFM (since it already
exists). Any PH program using that dictionary can then acess the file
normally.
regards
Richard Latimer
Wellington MIS Manager
Airways New Zealand
-----Original Message-----
From: george.j.wen@us.abb.com [mailto:george.j.wen@us.abb.com]
Sent: Saturday, 13 October 2001 4:45 a.m.
To: powerh-l@lists.swau.edu
Subject: QTP update error
Hello Listland,
We're on PH6.07 on an AS/400. Using PH on this system allows you to access
any
DB2 database file as a subfile in the event that file is not in your
Dictionary.
This is a
very nice feature and would be even nicer if the file could be updated via
QTP.
When
I try to update via QTP I get the error "Can't update an existing file that
isn't a
PowerHouse subfile." Does anyone know of a work around or way of doing
this???
Thanks,
GjW
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
Unsubscribe: "unsubscribe" in message body to
powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.
**********************************************************************
This electronic message together with any attachments is confidential. If
you receive it in error: (i) you must not use, disclose, copy or retain
it; (ii) please contact the sender immediately by reply email and then
delete the emails. Views expressed in this email may not be those of the
Airways Corporation of New Zealand Limited
**********************************************************************