Simplicty and flexibility!


Issues with @DFDDQLPrism using DEOS


Started by Rob Birney
Search
You will need to Sign In to be able to add or comment on the forum!

Issues with @DFDDQLPrism using DEOS

I have been bringing across procedures from a DFD 5.15i system using @DFDDQLPrism most of which have outputs.  While the procedures themselves appear to come across fine the format of the output rarely comes across working. 

So far I have encountered the following issues:

- In some cases no output format is brought across at all

- Where a column in summed in the procedure the command 'sum' is missing from the sum line of the output format e.g.

[{ORDERVAL:R13}] should be [{ORDERVAL:R13 sum}]

- The .end command is missing from some, it appears to be when no field in the procedure is summed.

- If the first field after .items is a date it misses off the opening square bracket e.g.

.items
{DATE:C10}]...

I'll keep you informed of anything else I encounter in regards to this.


Written by Rob Birney 10/03/16 at 10:56:38 Dataease [{8}]FIVE

Re:Issues with @DFDDQLPrism using DEOS

Hi Rob.

You are correct. The problem is that the format in DFD.

As this is "ancient" stuff it doesn't always fall the way we would think today. 

Our assumption when we started this project was that the DFD files would contain all the necessary information to regenerate the format as HTML in DE85.

But not true and most likely why DFD worked better than DFW.

We all know how you loose the formatting in DFW when you recompile a DQL while you in DFD didn't and that is due to the fact that the object in the layout is just linked to the column in DFW when in DFW it is linked to the actual object (price grouped level 3 sum). So when the levels change in DFW the link is lost, but in DFD it spans out from the items so the screen object will be "re-utilised" as long as it is in the right place in the layout.

The DFD way is much better from a human aspect, when the DFW way is the only "safe" way to do it in a programmer brain...

Anyhow, the consequence is that there is no way we can link up the layout and the DQL properly without running the DFD logic and rename objects according to the new model.... 

It would be possible, but not worthwhile...

So the DEDOS DFW DQl migration feature need to be seen as best as a developer "help" and not a proper migration tool from DFD to DE85.


Written by DataEase 10/03/16 at 12:44:17 Dataease [{8}]FIVE
DG3_ForumList