Easy to Create, Easy to Change - Easy to use!


Bug in export


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

Bug in export

Hi there,

there is this issue with the export function.

I have a simple procedure:

for TableName ;

list records

field1 ;

field2 ;

field3 .

for RelatedTable named "tRel" with ID = TableName ID ;

list records ;

field4;

field5;

field6.

end

end

export to "c:\export.txt" .

field1~field2~field3~field4~field5~field6

.items tRel
@f[1,1]~@f[1,2]~@f[1,3]~@f[2,1]~@f[2,2]~@f[2,3]
.end

That works IF no field is a derivation. In that case you can have the video output but if you try to export them you will get a crash. So the "solution" is to copy the derivation and put it instead of the field name (e.g. field6 has a derivation "lookup AnotherTable field9" you put "any AnotherTable field9"). This is boring but it works. But in case you have to export a lot of fields and each field has a derivation and the derived fields contains reference to other derivations you go from boring to a huge waste of time. I am in that situation and to me this is not a RAD is something that is something that is slowing me down. Please fix this because is really a problem.

Written by George Washington 05/02/15 at 15:22:00 Dataease [{8}]FIVE

Re:Bug in export

In my previous post I was not completely clear: the bug happens if the fields is a virtual field with a derivation.

Written by George Washington 06/02/15 at 10:39:32 Dataease [{8}]FIVE

Re:Re:Bug in export

No update on this?

Written by George Washington 09/02/15 at 15:17:14 Dataease [{8}]FIVE

Re:Re:Re:Bug in export

This export function is Outdated and will not be fixed.

Written by DataEase 10/02/15 at 12:04:03 Dataease [{8}]FIVE

Re:Re:Re:Re:Bug in export

Hi and thank you for your answer; the function will be replaced by an equivalent one or there will be no way to export data?

Written by George Washington 10/02/15 at 13:14:01 Dataease [{8}]FIVE

Re:Re:Re:Re:Re:Bug in export

Download Sample


Hi again.


I think our reply was a little to generic.

We have just tested export in DQL document and it works fine with Virtual fields.

So why it doesn't work with you is a "Mystery".

Might have to do with open relationships, migration or something like that.

I have included a sample that showcase the linear export the same as yours, and also how you can do it with ExecDQL.

ExecDQL can only export on ONE level, so you need to make sure you start with the lowest level and then simply "lookup" the columns from the higher level. You need to allocate them to temp variables if you want the export column name to be "legible". i.e. if you don't want any Customers Customername as the heading.

Username/Password: is high/high or you can start it directly from Startup.exe

Written by DataEase 11/02/15 at 11:58:01 Dataease [{8}]FIVE