ProgressDevelop
New Member
Hi All,
When an .esboe is generated from within Sonic Workbench we are not getting the final slash written to the procedure path element which causes us problems if the procedure is not in the root directory of the project.
E.g. Procedure ‘getCustomer.p’ in sub-directory ‘code’ of project. I.e. Full path is ‘code/getCustomer.p’.
The path generated in the .esboe file is: <wsad
rocPath>code</wsadrocPath> and not: <wsadrocPath>code/</wsadrocPath>
At runtime the call fails as the file ‘codegetCustomer’ is not found.
Either of the following 2 workarounds are working:
1. Renaming the .r to codegetCustomer.r and moving it into the root directory / propath; or
2. Manually adding the ‘/’ to the .esboe file
Is this a “feature” or is there a way to avoid using these manual processes?
OE 10.1C (10.1.2)
Sonic 7.6
Eclipse 3.2
Development : Vi$ta Business
Production: HP-UX Itanium
Cheers Keith
When an .esboe is generated from within Sonic Workbench we are not getting the final slash written to the procedure path element which causes us problems if the procedure is not in the root directory of the project.
E.g. Procedure ‘getCustomer.p’ in sub-directory ‘code’ of project. I.e. Full path is ‘code/getCustomer.p’.
The path generated in the .esboe file is: <wsad
rocPath>code</wsadrocPath> and not: <wsadrocPath>code/</wsadrocPath>At runtime the call fails as the file ‘codegetCustomer’ is not found.
Either of the following 2 workarounds are working:
1. Renaming the .r to codegetCustomer.r and moving it into the root directory / propath; or
2. Manually adding the ‘/’ to the .esboe file
Is this a “feature” or is there a way to avoid using these manual processes?
OE 10.1C (10.1.2)
Sonic 7.6
Eclipse 3.2
Development : Vi$ta Business
Production: HP-UX Itanium
Cheers Keith