Error with Progress

Cringer

ProgressTalk.com Moderator
Staff member
Without seeing what broker-set-attribute-list in broker.p does nobody will be able to help you I'm afraid.
 
Hi Cringer,

I believe that broker.p file came as part of the Progress Installation files. I am not sure where I would have to look for the broker-set-attribute-list.

I have included the entire log file below:

[12/01/17@15:12:29.175-0400] P-002740 T-001744 1 4GL -- Logging level set to = 2
[12/01/17@15:12:29.175-0400] P-002740 T-001744 1 4GL -- Log entry types activated: 4GLTrace
[12/01/17@15:12:31.816-0400] P-002740 T-001744 2 4GL 4GLTRACE Run ensure-broker [Main Block - mww-main.w @ 2796]
[12/01/17@15:12:31.816-0400] P-002740 T-001744 2 4GL 4GLTRACE Run get-attribute in ? "TYPE" [ensure-broker - mww-main.w @ 3186]
[12/01/17@15:12:31.816-0400] P-002740 T-001744 2 4GL 4GLTRACE Run adm/objects/broker.p PERSIST [ensure-broker - mww-main.w @ 3189]
[12/01/17@15:12:31.832-0400] P-002740 T-001744 2 4GL 4GLTRACE Run broker-set-attribute-list "1002 ADM-DEFAULT-DEACTIVATE-LINKS="NAVIGATION,TABLEIO,",ADM-NOTIFY-METHODS="exit,initialize,hide,view,enable,row-available,destroy,get-first,get-prev,get-next,get-last,open-query,add-record,update-record,copy-record,delete-record,reposition-query,reset-record,cancel-record,",ADM-NOTIFY-LINKS="CONTAINER-SOURCE,CONTAINER-TARGET,CONTAINER-TARGET,CONTAINER-TARGET,CONTAINER-TARGET,RECORD-TARGET,CONTAINER-TARGET,NAVIGATION-TARGET,NAVIGATION-TARGET,NAVIGATION-TARGET,NAVIGATION-TARGE
[12/01/17@15:12:31.832-0400] P-002740 T-001744 2 4GL 4GLTRACE Run set-ADM-DEFAULT-DEACTIVATE-LINKS in adm/objects/broker.p "NAVIGATION,TABLEIO" [broker-set-attribute-list - adm/objects/broker.p @ 6523]
[12/01/17@15:12:31.832-0400] P-002740 T-001744 2 4GL 4GLTRACE Run use-ADM-DEFAULT-DEACTIVATE-LINKS in adm/objects/broker.p "NAVIGATION,TABLEIO" [broker-set-attribute-list - adm/objects/broker.p @ 6552]
[12/01/17@15:12:31.832-0400] P-002740 T-001744 2 4GL 4GLTRACE Run set-ADM-NOTIFY-METHODS in adm/objects/broker.p "exit,initialize,hide,view,enable,row-available,destroy,get-first,get-prev,get-next,get-last,open-query,add-record,update-record,copy-record,delete-record,reposition-query,reset-record,cancel-record" [broker-set-attribute-list - adm/objects/broker.p @ 6523]
[12/01/17@15:12:31.832-0400] P-002740 T-001744 2 4GL 4GLTRACE Run use-ADM-NOTIFY-METHODS in adm/objects/broker.p "exit,initialize,hide,view,enable,row-available,destroy,get-first,get-prev,get-next,get-last,open-query,add-record,update-record,copy-record,delete-record,reposition-query,reset-record,cancel-record" [broker-set-attribute-list - adm/objects/broker.p @ 6552]
[12/01/17@15:12:31.832-0400] P-002740 T-001744 2 4GL 4GLTRACE Run set-ADM-NOTIFY-LINKS in adm/objects/broker.p "CONTAINER-SOURCE,CONTAINER-TARGET,CONTAINER-TARGET,CONTAINER-TARGET,CONTAINER-TARGET,RECORD-TARGET,CONTAINER-TARGET,NAVIGATION-TARGET,NAVIGATION-TARGET,NAVIGATION-TARGET,NAVIGATION-TARGET,RECORD-SOURCE,TABLEIO-TARGET,TABLEIO-TARGET,TABLEIO-TARGET,TABLEIO-TARGET,RECORD-SOURCE,TABLEIO-TARGET,TABLEIO-TARGET" [broker-set-attribute-list - adm/objects/broker.p @ 6523]
[12/01/17@15:12:31.832-0400] P-002740 T-001744 2 4GL 4GLTRACE Run use-ADM-NOTIFY-LINKS in adm/objects/broker.p "CONTAINER-SOURCE,CONTAINER-TARGET,CONTAINER-TARGET,CONTAINER-TARGET,CONTAINER-TARGET,RECORD-TARGET,CONTAINER-TARGET,NAVIGATION-TARGET,NAVIGATION-TARGET,NAVIGATION-TARGET,NAVIGATION-TARGET,RECORD-SOURCE,TABLEIO-TARGET,TABLEIO-TARGET,TABLEIO-TARGET,TABLEIO-TARGET,RECORD-SOURCE,TABLEIO-TARGET,TABLEIO-TARGET" [broker-set-attribute-list - adm/objects/broker.p @ 6552]
[12/01/17@15:12:31.832-0400] P-002740 T-001744 2 4GL 4GLTRACE Run set-ADM-STATE-NAMES in adm/objects/broker.p "link-changed,record-available,no-record-available,update-begin,update,update-complete,first-record,last-record,only-record,not-first-or-last,delete-complete,no-external-record-available" [broker-set-attribute-list - adm/objects/broker.p @ 6523]
[12/01/17@15:12:31.832-0400] P-002740 T-001744 2 4GL 4GLTRACE Run use-ADM-STATE-NAMES in adm/objects/broker.p "link-changed,record-available,no-record-available,update-begin,update,update-complete,first-record,last-record,only-record,not-first-or-last,delete-complete,no-external-record-available" [broker-set-attribute-list - adm/objects/broker.p @ 6552]
[12/01/17@15:12:31.832-0400] P-002740 T-001744 2 4GL 4GLTRACE Run set-ADM-STATE-LINKS in adm/objects/broker.p "*;TABLEIO-SOURCE,NAVIGATION-SOURCE;TABLEIO-SOURCE,NAVIGATION-SOURCE;TABLEIO-TARGET;TABLEIO-SOURCE,RECORD-SOURCE,NAVIGATION-SOURCE;TABLEIO-SOURCE,RECORD-SOURCE,NAVIGATION-SOURCE;NAVIGATION-SOURCE;NAVIGATION-SOURCE;NAVIGATION-SOURCE;NAVIGATION-SOURCE;RECORD-SOURCE;TABLEIO-SOURCE,NAVIGATION-SOURCE;" [broker-set-attribute-list - adm/objects/broker.p @ 6523]
[12/01/17@15:12:31.832-0400] P-002740 T-001744 2 4GL 4GLTRACE Run use-ADM-STATE-LINKS in adm/objects/broker.p "*;TABLEIO-SOURCE,NAVIGATION-SOURCE;TABLEIO-SOURCE,NAVIGATION-SOURCE;TABLEIO-TARGET;TABLEIO-SOURCE,RECORD-SOURCE,NAVIGATION-SOURCE;TABLEIO-SOURCE,RECORD-SOURCE,NAVIGATION-SOURCE;NAVIGATION-SOURCE;NAVIGATION-SOURCE;NAVIGATION-SOURCE;NAVIGATION-SOURCE;RECORD-SOURCE;TABLEIO-SOURCE,NAVIGATION-SOURCE;" [broker-set-attribute-list - adm/objects/broker.p @ 6552]
[12/01/17@15:12:31.832-0400] P-002740 T-001744 2 4GL 4GLTRACE Run set-ADM-PASS-THROUGH-LINKS in adm/objects/broker.p "NAVIGATION,TABLEIO,RECORD" [broker-set-attribute-list - adm/objects/broker.p @ 6523]
[12/01/17@15:12:31.832-0400] P-002740 T-001744 2 4GL 4GLTRACE Run use-ADM-PASS-THROUGH-LINKS in adm/objects/broker.p "NAVIGATION,TABLEIO,RECORD" [broker-set-attribute-list - adm/objects/broker.p @ 6552]
[12/01/17@15:12:31.832-0400] P-002740 T-001744 2 4GL 4GLTRACE Run set-ADM-CIRCULAR-LINKS in adm/objects/broker.p "RECORD" [broker-set-attribute-list - adm/objects/broker.p @ 6523]
[12/01/17@15:12:31.832-0400] P-002740 T-001744 2 4GL 4GLTRACE Run use-ADM-CIRCULAR-LINKS in adm/objects/broker.p "RECORD" [broker-set-attribute-list - adm/objects/broker.p @ 6552]
[12/01/17@15:12:31.832-0400] P-002740 T-001744 2 4GL 4GLTRACE Run set-ADM-TRANSLATION-ATTRS in adm/objects/broker.p "FOLDER-LABELS,LABEL" [broker-set-attribute-list - adm/objects/broker.p @ 6523]
[12/01/17@15:12:31.832-0400] P-002740 T-001744 2 4GL 4GLTRACE Run use-ADM-TRANSLATION-ATTRS in adm/objects/broker.p "FOLDER-LABELS,LABEL" [broker-set-attribute-list - adm/objects/broker.p @ 6552]
[12/01/17@15:12:31.832-0400] P-002740 T-001744 2 4GL 4GLTRACE Run set-ADM-TRANS-METHODS in adm/objects/broker.p "delete-record" [broker-set-attribute-list - adm/objects/broker.p @ 6523]
[12/01/17@15:12:31.832-0400] P-002740 T-001744 2 4GL 4GLTRACE Run use-ADM-TRANS-METHODS in adm/objects/broker.p "delete-record" [broker-set-attribute-list - adm/objects/broker.p @ 6552]
[12/01/17@15:12:31.832-0400] P-002740 T-001744 2 4GL 4GLTRACE Run set-ADM-PRE-INITIALIZE-EVENTS in adm/objects/broker.p "initialize,create-objects,change-page,destroy,edit-attribute-list" [broker-set-attribute-list - adm/objects/broker.p @ 6523]
[12/01/17@15:12:31.832-0400] P-002740 T-001744 2 4GL 4GLTRACE Run use-ADM-PRE-INITIALIZE-EVENTS in adm/objects/broker.p "initialize,create-objects,change-page,destroy,edit-attribute-list" [broker-set-attribute-list - adm/objects/broker.p @ 6552]
[12/01/17@15:12:31.847-0400] P-002740 T-001744 2 4GL 4GLTRACE Run set-broker-owner in adm/objects/broker.p "1003" [ensure-broker - mww-main.w @ 3190]
[12/01/17@15:12:31.847-0400] P-002740 T-001744 2 4GL 4GLTRACE Run set-attribute-list "CURRENT-PAGE=0,ADM-OBJECT-HANDLE=1000" [Main Block - mww-main.w @ 3408]
[12/01/17@15:12:31.847-0400] P-002740 T-001744 2 4GL 4GLTRACE Run ensure-broker [set-attribute-list - mww-main.w @ 3322]
[12/01/17@15:12:31.847-0400] P-002740 T-001744 2 4GL 4GLTRACE Run get-attribute in adm/objects/broker.p "TYPE" [ensure-broker - mww-main.w @ 3186]
[12/01/17@15:12:31.847-0400] P-002740 T-001744 2 4GL 4GLTRACE Run broker-get-attribute in adm/objects/broker.p "1002 TYPE" [get-attribute - adm/objects/broker.p @ 875]
[12/01/17@15:12:31.847-0400] P-002740 T-001744 2 4GL 4GLTRACE Run broker-set-attribute-list in adm/objects/broker.p "1003 CURRENT-PAGE=0,ADM-OBJECT-HANDLE=1000" [set-attribute-list - mww-main.w @ 3325]
[12/01/17@15:12:31.847-0400] P-002740 T-001744 1 4GL -- (Procedure: 'broker-set-attribute-list adm/objects/broker.p' Line:6505) Entry 19 is outside the range of list ^^. (560)
[12/01/17@15:12:31.847-0400] P-002740 T-001744 2 4GL 4GLTRACE Run bg-load-icon [Main Block - mww-main.w @ 5748]
[12/01/17@15:12:31.847-0400] P-002740 T-001744 2 4GL 4GLTRACE Run get-attribute in adm/objects/broker.p "bg-system-icon" [bg-load-icon - mww-main.w @ 4226]
[12/01/17@15:12:31.847-0400] P-002740 T-001744 2 4GL 4GLTRACE Run broker-get-attribute in adm/objects/broker.p "1002 bg-system-icon" [get-attribute - adm/objects/broker.p @ 875]
[12/01/17@15:12:31.847-0400] P-002740 T-001744 2 4GL 4GLTRACE Run get-bg-system-icon in adm/objects/broker.p [broker-get-attribute - adm/objects/broker.p @ 4515]
[12/01/17@15:12:31.847-0400] P-002740 T-001744 2 4GL 4GLTRACE Run splash.w [Main Block - mww-main.w @ 5749]
[12/01/17@15:12:31.847-0400] P-002740 T-001744 2 4GL 4GLTRACE Run ensure-broker [Main Block - splash.w @ 529]
[12/01/17@15:12:31.847-0400] P-002740 T-001744 2 4GL 4GLTRACE Run get-attribute in adm/objects/broker.p "TYPE" [ensure-broker - splash.w @ 919]
[12/01/17@15:12:31.847-0400] P-002740 T-001744 2 4GL 4GLTRACE Run broker-get-attribute in adm/objects/broker.p "1002 TYPE" [get-attribute - adm/objects/broker.p @ 875]
[12/01/17@15:12:31.847-0400] P-002740 T-001744 2 4GL 4GLTRACE Run get-attribute in adm/objects/broker.p "bg-system-icon" [Main Block - splash.w @ 1186]
[12/01/17@15:12:31.847-0400] P-002740 T-001744 2 4GL 4GLTRACE Run broker-get-attribute in adm/objects/broker.p "1002 bg-system-icon" [get-attribute - adm/objects/broker.p @ 875]
[12/01/17@15:12:31.847-0400] P-002740 T-001744 2 4GL 4GLTRACE Run get-bg-system-icon in adm/objects/broker.p [broker-get-attribute - adm/objects/broker.p @ 4515]
[12/01/17@15:12:31.847-0400] P-002740 T-001744 2 4GL 4GLTRACE Run enable_UI [Main Block - splash.w @ 1231]
[12/01/17@15:12:35.128-0400] P-002740 T-001744 2 4GL 4GLTRACE Run disable_UI [USER-INTERFACE-TRIGGER - splash.w @ 1215]
[12/01/17@15:12:35.128-0400] P-002740 T-001744 2 4GL 4GLTRACE Run dispatch "create-objects" [Main Block - mww-main.w @ 6670]
[12/01/17@15:12:35.128-0400] P-002740 T-001744 2 4GL 4GLTRACE Run broker-dispatch in adm/objects/broker.p "1003 create-objects" [dispatch - mww-main.w @ 3164]
[12/01/17@15:12:35.128-0400] P-002740 T-001744 1 4GL -- (Procedure: 'broker-dispatch adm/objects/broker.p' Line:4139) Entry 17 is outside the range of list ^^. (560)
[12/01/17@15:12:36.316-0400] P-002740 T-001744 2 4GL 4GLTRACE Run dispatch "initialize" [Main Block - mww-main.w @ 6685]
[12/01/17@15:12:36.316-0400] P-002740 T-001744 2 4GL 4GLTRACE Run broker-dispatch in adm/objects/broker.p "1003 initialize" [dispatch - mww-main.w @ 3164]
[12/01/17@15:12:36.316-0400] P-002740 T-001744 1 4GL -- (Procedure: 'broker-dispatch adm/objects/broker.p' Line:4139) Entry 17 is outside the range of list ^^. (560)
 

Stefan

Well-Known Member
Hi Cringer,

I believe that broker.p file came as part of the Progress Installation files. I am not sure where I would have to look for the broker-set-attribute-list.

I have included the entire log file below:

So your application is using ADM1 (or so) - I have never used this so I may be talking nonsense. Anyway the ^^ comes from broker.p (available in %dlc%/src/adm/objects/broker.p). If you COMPILE this with the DEBUG-LIST option you will get line numbers that match up with your log above. The 'offending' part comes due to :ADM-DATA being empty...

Code:
     6399     IF p-caller:ADM-DATA = "":U OR p-caller:ADM-DATA = ? THEN
     6400         p-caller:ADM-DATA = "~^~^":U.

When it probably shouldn't be empty.

You stated that you are using a vendor's app. I think you will need to either:

a. use the same version adm framework as that with which the vendor app was compiled (ensure that the %dlc%/src/adm directory of that Progress version is earlier in the propath than your installation)

or

b. ensure that the entire application is compiled with references to your version of %dlc%/src/adm is ahead of any vendor code

This may be a good point to contact your vendor.
 

Rob Fitzpatrick

ProgressTalk.com Sponsor
Hi Tom,

I was able to find the .pf startup file and I added the session startup parameter.

What was the name and location of this file? Was it a .pf referenced by your specific application shortcut, or was it a file called startup.pf location in your DLC directory? If the latter, note that modifying it may have unintended consequences, as its startup parameters are added to every session you run in any application, including utilities that run as database clients.

The point is that application-specific session startup parameters should go in application specific parameter files.
 

TomBascom

Curmudgeon
This is the classic problem with ADM based applications. You MUST make sure that you compile with the exact same version of the ADM that the code was developed with -- right down to the service pack level.

So your application is using ADM1 (or so) - I have never used this so I may be talking nonsense. Anyway the ^^ comes from broker.p (available in %dlc%/src/adm/objects/broker.p). If you COMPILE this with the DEBUG-LIST option you will get line numbers that match up with your log above. The 'offending' part comes due to :ADM-DATA being empty...

Code:
     6399     IF p-caller:ADM-DATA = "":U OR p-caller:ADM-DATA = ? THEN
     6400         p-caller:ADM-DATA = "~^~^":U.

When it probably shouldn't be empty.

You stated that you are using a vendor's app. I think you will need to either:

a. use the same version adm framework as that with which the vendor app was compiled (ensure that the %dlc%/src/adm directory of that Progress version is earlier in the propath than your installation)

or

b. ensure that the entire application is compiled with references to your version of %dlc%/src/adm is ahead of any vendor code

This may be a good point to contact your vendor.
 

RealHeavyDude

Well-Known Member
Having worked a lot with ADM1/AMD2 years ago there is one thing you must understand: As soon as you start using it you should take a copy of the adm or adm2 directory and add it to your PROPATH before the entries pointing in your Progress/OpenEdge installation. Thus the ADM should become part of your application. Of course you can still upgrade your Progress installation - compile everything and there you go almost without a fuzz. Having your PROPATH pointing to the ADM in the Progress/OpenEdge installation means that there is a big chance (maybe not nowadays anymore as I don't think there is still much development work done on them) that something within it has been changed so that you need to change your application too. That change can be as trivial as adding an additional parameter that was added to an API that you use up to the need to re-create your object. BTW, the same is true for Dynamics. Bottom line: When the application is in a stable state you should "freeze" the ADM in using a copy, not the one that comes with the installation. Heavy Regards, RealHeavyDude.
 
The startup application is not startup.pf. It's called loanstest.pf.

The application is currently running on another server using Progress 9.1E.

Should I copy the adm folder from that server to this server that's running OpenEdge 10?

Could you guide me through the steps?
 

RealHeavyDude

Well-Known Member
Just to be clear:

Having installed a development license, the installation directory contains a gui, tty and src directory. The gui (graphical client) directory contains the with the prowin32.exe compiled files whereas the tty (character client) directory contains the with _progres.exe compiled files. The src folder contains the source code. AFAIK, depending on the license (run time) you have installed it might not even contain the adm, adm2 or dynamics directories in the gui or tty directories. In that case you just copy the compiled version from a development installation of the same version (down to the patch level) for gui or tty - according to what you need.

What you need to do:

ADM Runtime:

Since you can't run V9 compiled code under OE10 you must take a copy of the source code from a development installation (src/adm) and then compile that copy with your OE10 developers license. In that case the compiled files will end up in the src directory structure but I never cared about that. Just a note: There are references to include files outside of the adm directory within src. Therefore, in order to successfully compile the ADM you need to have the whole src directory from V9 in the PROPATH.

Your application:

You need to make sure that you comile your application with the src/adm directory copied from V9 in the PROPATH before the one from the OE10 installation.

If you miss source code:

There have been version of V9 and OE10 which did not contain all necessary source code (namely include file references outside of the adm - for example adecomm I think) because Progress did not ship them. If you run into that problem you need to raise it with the Progress tech support so that they provide them to you. Other than that you might be lucky to get them from somebody else who has them for some reason. I don't have any Progress V9 at my disposal so I am afraid I can't provide them to you if you run into that problem.

Heavy Regards, RealHeavyDude.
 
Hi RealHeavyDude,

I just need to be clear on a few things.

My queries are below:

I checked the gui and tty folders (OpenEdge 10) installation. For the gui folder, the adm folder is there but missing the template and methods folders. The tty folder doesn't have the adm folder. Should I copy the adm folder from src over to tty and gui folders?

ADM runtime
Create a backup of the V10 src/adm folder before I copy v9 src/adm or should I just overwrite it? Where do I compile the files? Can it be done via Application Compiler? I have 4GL Development licence.


Application
The application was copied across to the new server with the database converted to V10. The vendor indicated that the V9 adm source files are also in a folder within the application.

When I compile the application, those files are also compiled. The folder is placed higher than the V10 version in PROPATH. Should I add the application folders then the v10 version in the application compilation list?

i: drive maps to progress folder
J:\ maps to the application folder


compiler.GIF
 

Stefan

Well-Known Member
I checked the gui and tty folders (OpenEdge 10) installation. For the gui folder, the adm folder is there but missing the template and methods folders. The tty folder doesn't have the adm folder. Should I copy the adm folder from src over to tty and gui folders?

ADM runtime
Create a backup of the V10 src/adm folder before I copy v9 src/adm or should I just overwrite it? Where do I compile the files? Can it be done via Application Compiler? I have 4GL Development licence.

You should not be copying anything over your oe10 installation, you should include the v9 adm sources in 'your application' and ensure that they are in your propath when compiling.

Application
The application was copied across to the new server with the database converted to V10. The vendor indicated that the V9 adm source files are also in a folder within the application.

Hurrah, you don't have to copy anything at all.

When I compile the application, those files are also compiled. The folder is placed higher than the V10 version in PROPATH. Should I add the application folders then the v10 version in the application compilation list?

i: drive maps to progress folder
J:\ maps to the application folder

You only need to ensure the v9 adm is first in your propath - this will automatically eclipse any v10 adm sources (unless you are missing v9 files).

So you should not have i:\src in your propath, you should have j:\bgiwtest\src in your propath and j:\bgiwtest\src must have the adm directory below it (which should already be the case if the v9 adm source files are supplied with your vendor's code). If they are not, but are in (for example) j:\bgiwtest\src\v9\adm then you will need to add j:\bgiwtest\src\v9 to your propath too.

Some files may no longer compile (for example due to defining variables as keywords that are new in oe10) - in that case you can add these to the keyword forget list.
 

tamhas

ProgressTalk.com Sponsor
To possibly clarify Stefan's point a little. When one develops an application using the ADM framework, the ADM code is just more ABL, just ABL that one doesn't have to write. This framework evolves from version to version, sometimes in small ways and sometimes in very big ways. It would be lovely if one could take an old application and compile it against the new framework and it would just magically work, but sadly this is not the case. Sometimes, modifying the application to use the new version of the framework can be non-trivial. In particular, there is the suggestion here that you have an application which expects ADM1, but we have been on ADM2 for quite some time and that is a non-trivial switch. It is enough of a switch that you would probably expect the vendor to be the one to make the accommodation. To avoid that, make a copy of the ADM code from the prior version, install that somewhere, and put it on the PROPATH ahead of whatever ADM code might be in the new version. In fact, I wouldn't include the new ADM code in the path at all. *Then* compile on the new version of Progress. Then you will have consistent code.
 
Good morning all,

I am still having the same issue and I have removed i:\src from the Propath. I am not sure if my propath is correct. Should I also include the Progress Files in the PROPATH as well?

Vendor Reply:
Unfortunately we have no experience with V10 Progress. And nearly all of our clients have converted to.Net and SQL Server, so I don’t think that any of them do either.

I’m sorry. Once we committed to .Net, we froze our Progress environments on 9.1e and have not invested any time in upgrades.

Below is the PROPATH in the environment.propath2.GIFpropath1.GIF
 

RealHeavyDude

Well-Known Member
Honestly - I think you are not in the position to solve this problem on your own unless you take a training. But a training on adm will be hard to get as we are talking about a frame work that is just a few years shy of being 20 years old. But the frame work is not the root of your problems - therefore I think you should involve a consultant with experience on this thing. It will save you a lot of time and you will see that it will run without a fuzz if you set up the environment correctly.

Short answer: You need to include everything in the PROPATH that is needed in order to compile successfully. I can't tell you for the application - but for sure you need the src/adm folder from V9 in your PROPATH. The vendor mentioned that they shipped the adm folder - if that's the case they just need to tell you how you need to set the PROPATH in order to successfully compile it under V9 with a V9 installation. Having that information it's easy to tweak the PROPATH so that it will compile with and OE10 installation.

Heavy Regards, RealHeavyDude.
 

Cringer

ProgressTalk.com Moderator
Staff member
I can only agree with RHD. The questions you are asking across this board suggest you really have little idea about how Progress works. It will be invaluable to either get some basic Progress training, or to get a consultant in who can talk you through everything you need to know. You won't find the level of assistance you need here as we can only see a tiny snapshot of what is happening. You need someone on site to work it through with you.
 
Hi All,

Thank you for the assistance and you are right, I have really little knowledge of how Progress works. I will find out from the Project Manager the best way forward.

Regards,
Renee
 

RealHeavyDude

Well-Known Member
YEAH!!! You are my man!

Giving the project manager a chance to do something that is valuable to the project is one of my all-time favorites.

Heavy Regards, RealHeavyDude.
 
Top