Looking for specs in wrong pathcode

[DeRay_Scholz]

Hello all:

I have a situation that I hope someone can help with. Here it goes:

One of our developers has created a new report for label printing. She copied an existing report in CRP, made modifications, tested, checked in.

We then transferred the report to PROD and created new versions and checked in. The problem is this: When we run the report locally, it is looking for the spec files and dll under the CRP pathcode (ie. e:\b7\crpb733\spec\gbltbl.xdb). Since all of our PROD users do not have the CRP pathcode on their machines, the job fails.

Does anyone know where it is pulling this information from?

PS - We also did a test by copying the working report in PROD, completely eliminating any link to CRP, but it still looks for the specs and dlls under the CRP path.

Any thoughts?

Thanks,
DeRay Scholz
The Upper Deck Company
OW B733.2 SP11.1 , WIN2000, SQL2000

 

[Zoltan_Gyimesi]

Hi DeRay,
Your issue is really strange.
"cbruce" have replied a thread about 2-3 weeks ago on this Forum, describing the spec location settings in jde.ini.
Let me simply to copy his reply here.
Please, let us know if you found what caused or what resolved this problem. Personally me, I am very curious to it. Thanks.
Zoltán
=======================cbruce have written============================
cbruce
(stranger )
8/2/01 04:14 PM
Re: Location of DDDICT / DDTEXT / GLBLTBL [Üzenet#: 18034 / re: 17849 ]


Bill,

Your request is quite unusual. First of all, realize that DDDICT, DDTEXT, and GLBLTBL are cache TAM files. This means they are essentially temporary and dispensible. Each of these files is a replicated version of DD and table specs in your Central RDB.

To answer your question on where JDE expects to find these files; the answer is in the JDE.INI. In the install section of the INI, there is a subkey in the [INSTALLS] key called "B733=C:\b7". The value of this key is the root of the OneWorld install on the client. There is another subkey under the [SVR] key that is called "SpecPath=spec". Hence in this case, "C:\b7\spec" is the directory where OneWorld writes and reads DDDICT, DDTEXT, and GLBLTBL.

Good luck in whatever you are doing...
======================En of cbruce's post=============================

B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)

 

[David Robertson]

Zoltan,
just a quick correction. There is no (at least not normally) c:/b7/spec directory. The drive letter, of course depends where you installed it, but the specs normally live at c:/b7/pathcode/spec.

Dave

 

[Zoltan_Gyimesi]

Dave,

Thank you for your correction.
Cbruce's post was clear for me in my own interpretation.
He wrote about key "B733=C:\b7" in the [INSTALLS] section:
"The value of this key is the root of the OneWorld install on the client."
The keyword was the ROOT for me. Hence, this key determines not only the spec location but all the subfolder structure of OneWorld install.
I suppose, the subfolder structure under B7 is hardcoded, so it was obvious for me, if the key is "B733=C:\b7" then the spec will be reside in "c:\b7\pathcode\spec" subfolder.
OK, it was obvious for me but maybe it wasn't for all of us, so thanks again for your clarification.

Regards,
Zoltán

B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)

 

[DeRay_Scholz]

Adrian,

The Override environment in the advanced tab on report properties was the
answer. Thank you so much for your input.

DeRay

 

[Adrian_Chimirel]

Now this is Adriano's reply (found it on the OW Xe forum):



Hi DeRay,

Can you check the report properties and check if someone entered an Override environment in the Advanced tab. If so, remove it and it should work. I have encounted this problem.

Adrian

Valmatrix Consulting Inc.