Recent content by paul_pichette

Ok, thanks for sharing your experience. Currently the small application doesn't have 2 SDO's for the same table, what problem would that cause? (I guess this question is probably because I haven't used the EndTransactionValidate Override...). Paul.

I would expect ADM2 & Appserver integration to behave more than just 'fairly'... Any particular pitfalls you remember that caused you to shift gears and develop your own function calls to the Appserver? And do you then not use the SDV/SDB - SDO (rowobject) mechanism? Paul.

Couldn't find much help in the Progress Knowledgebases, so I thought I would give you all a try... How complex is it to make a standard ADM2 (using core objects) to work with the Appserver? Any suggestions of nightime reading material I should have? 9.1C

typically, you would look at every line that says something like: ^FIELD <REF-FIELD-IN-JETFORMS> <FIELD VALUE TO MERGE> ^FIELD <REF-FIELD-IN-JETFORMS> <FIELD VALUE TO MERGE> ... This is the basis for the merging. So the <REF-FIELD-IN-JETFORMS> actually refers to the field that was...

You know, I haven't even looked at my program this morning, but I'm sure what you say is true. Because the default for a browser is to not have any enabled fields... Is there a smart Dynamic Data Browser out there? ;-) Paul

Yes, the whole SBT2 is disabled. I didn't check the SDB2... What instance attributes could affect the toolbar? Remember, I have smartlinks setup the same way I would with a SDV instead of a SDB and it works for the SDV. It seems to me that Progress doesn't do the TABLEIO too well with...

I want to be able to link a basic maintenance screen (SDO-STB-SDV) to a detailled table (SDO-STB-SDB). The detailled table toolbar becomes disabled by default, replacing that SDB with an equivalent SDV, it works. Here's the mapping: SDO1-DATA-SDV1 SDV1-UPDATE-SDO1 STB1-TABLEIO-SDV1...

One thing I noticed is that the query will not send any information if the foreign key fields make sense... I had mistyped the table name in the string, and it was not considering the mapping requirement, but not telling me I made a mistake! I had to double back on my steps and find the error...

Another question has popped up, that I can't find in the on-line help (v 9.1.c). When you design a maintenance screen to have key fields that are updatable only in 'add' mode, how do you enable the field so that it is a required key field? I think that in ADM 1, we had an ADM-CREATE-FIELD...

It worked. Thanks

I was wondering that there might be a way to set the foreign key fields this way. You can't force the set foreign key fields dialog box to appear once you've dropped smart objects, and in my situation, it wasn't appearing! Thanks!

The thing is that I have the SDO for the contact in the smartdataviewer to support the smart select, and the client sdo is this smartwindow, when I drop the smartdataviewer in the smartwindow, it doesn't try to link foreign key fields? Is it because the SDO are not both in the same smartwindow?

9.1C So I wanted to use the SmartSelect to lookup possible values for a field as a combo box... Thing is that the values shown are dependent on another SDO: CLIENT SDO -DATA-> CLIENT SDV In the CLIENT SDV, I have a SmartSelect, with a reference to the CONTACT SDO that is in the SDV -...