Hi All
I am facing a strange problem using a mixture of 6.5 Build 444 and 6.5.1
release.
My developer is on 6.5 Build 444 and I am on 6.5.1.
There is one pbl which works as per the business rules and gets regenerated
properly in 6.5, I mean all the window in it work according to the
specification of the project. But when we bring the PBL to the Integration
point to integrate the whole in 6.5.1, it behaves in the ad-hoc manner,
resulting delays in data retrieval and many other things where we change
font colors of the row based on certain criteria.
When I try to regenerate the pbl from 6.5.1 I receive the following error
listed in the file attached.
What happens is that after this if I transfer this pbl to build 444 then
there also it will start behaving in a different manner, until I change the
pbl by getting it from the backup.
Could anybody pls. highlight their views and solutions on this issue, any
advise for actions to be taken.
This matter is quiet urgent as we have to complete the Integration this week
and next week the system is to be test implemented for UAT.
<<errors.txt>>
My environment is PB 6.5 +++
Windows NT Workstation 4.0 SP 3
Backend Oracle 8.0.4
FrameWork : PFC 6.5++
> Remain Kooollll......,
> Mohamed Ashraf Memon
> Advanced Micro Devices (Singapore)
> TEL : 7969-888 X 39826
> FAX : 4492-360
> DID : 7969-826
> Email : [EMAIL PROTECTED]
>
>
>
Library: r:\ritsstr.pbl
Object: w_str_lot_attach
Object Variable Declarations
(0001): Information C0146: The identifier 'w_str_lot_attach' conflicts
with an existing global variable with this name. The new definition of
'w_str_lot_attach' will take precedence and the prior value will be ignored until this
version of 'w_str_lot_attach' goes out of scope
Object: w_str_lot_attach_confirm
Object Variable Declarations
(0001): Information C0146: The identifier 'w_str_lot_attach_confirm'
conflicts with an existing global variable with this name. The new definition of
'w_str_lot_attach_confirm' will take precedence and the prior value will be ignored
until this version of 'w_str_lot_attach_confirm' goes out of scope
Object: w_str_lot_attach_deledit_confirm
Object Variable Declarations
(0001): Information C0146: The identifier
'w_str_lot_attach_deledit_confirm' conflicts with an existing global variable with
this name. The new definition of 'w_str_lot_attach_deledit_confirm' will take
precedence and the prior value will be ignored until this version of
'w_str_lot_attach_deledit_confirm' goes out of scope
Object: w_str_lot_attach_delete
Object Variable Declarations
(0001): Information C0146: The identifier 'w_str_lot_attach_delete'
conflicts with an existing global variable with this name. The new definition of
'w_str_lot_attach_delete' will take precedence and the prior value will be ignored
until this version of 'w_str_lot_attach_delete' goes out of scope
Object: w_str_lot_create
Object Variable Declarations
(0001): Information C0146: The identifier 'w_str_lot_create' conflicts
with an existing global variable with this name. The new definition of
'w_str_lot_create' will take precedence and the prior value will be ignored until this
version of 'w_str_lot_create' goes out of scope
Object: w_str_lot_delete
Object Variable Declarations
(0001): Information C0146: The identifier 'w_str_lot_delete' conflicts
with an existing global variable with this name. The new definition of
'w_str_lot_delete' will take precedence and the prior value will be ignored until this
version of 'w_str_lot_delete' goes out of scope
Object: w_str_lot_issue_template
Object Variable Declarations
(0001): Information C0146: The identifier 'w_str_lot_issue_template'
conflicts with an existing global variable with this name. The new definition of
'w_str_lot_issue_template' will take precedence and the prior value will be ignored
until this version of 'w_str_lot_issue_template' goes out of scope
Object: w_temp
Object Variable Declarations
(0001): Information C0146: The identifier 'w_temp' conflicts with an
existing global variable with this name. The new definition of 'w_temp' will take
precedence and the prior value will be ignored until this version of 'w_temp' goes out
of scope
