They are using 19.1 (not the last build).
Type: Posts; User: Sam Neuner
They are using 19.1 (not the last build).
That info would help - installing Plato.
In the dialog that pops up when Dataflex 2020 is not installed, "we advice you to install this version" should be we advise you ...".
The latest 19.1 version?
"Order By" is a valid SQL expression. "Select * from Customer Where State = 'NY' Order By Last_Name".
I think this was a bug that was corrected in the latest version 19.2?
I modified the SaveRecord function to receive a Handle array of all changed DDs.
Obviously you would need to check each child object in the function. I just used two DDs in this example to keep it simple.
I modified the save in case the F2 is pressed:
Procedure Request_Save
Boolean bErr
Integer iNo
Handle hoDD
Move 0 to hoDD
Also, if you want the child objects to use the View's Request_Save when the "Save" is executed from a child column and the Server is set in the object, you need to "Set DEO_Delegate_Mode to...
If neither is changed the "Save" icon is shadowed!
This appears to work:
Put this code in the Main_DD:
Function Should_Save Returns Boolean
Boolean bShould_Save
Forward Get Should_Save...
Changing the "Should_Save" to "Changed_State" works!
When I put this into the main (parent) DD I get an Access Violation Error as soon as the view is activated.
The problem is not when the "Save" is executed from a child column but from a parent column. If only a child column is changed and not a parent column, the "Save" icon is shadowed when the user is...
I you change the child but do not change the parent and the user happens to be in a parent column when trying to save, the "Save" icon is shadowed (but F2 works).
I am not "sending" the save, I am clicking on the "Save" icon. If the focus is on a column bound to the parent, the save is sent to the parent DD. The issue is how to send it to the child DD if...
The main issue is not sending from one child to another, but from the Parent to the Child and that is where the Reentrancy is at issue!
Yes you understand my issue and what you said is everything I have already stated (I think). Reentrancy is a problem if you try to send to child DDs and you are in the Parent.
I am not sending the Request_Save, I am clicking on the "Save" icon on the toolbar or press F2. Yes, the saves propagate up, that is what prompted my original question. The Request_Save goes to...
Here are the DDs (to test, I created them from scratch with nothing else added):
Class cProjectDataDictionary is a DataDictionary
Procedure Construct_Object
Forward Send...
Yes, the relationship is working.
This does not work, what is wrong. When I put a stop at both saves it does not go through the oDevData_DD.
Object oSaveTest is a dbView
Set Location to 5 5
Set Size to 156 290
Set...
When you have a dbView with a mix of parent and child fields on it, how do you take care of the "Saves"? If the user is on a parent column the save will be sent to the parent DD and the child does...
Why does it work without the Cast when the = is a constant "50" or an integer variable "iNumber"?