Hi

BTW: I am using version 8.2.0.1619. Not sure whether this makes any difference.

I thought this was an issue with my client?s database.

But, since this is happening on a second database (different client).

I am pretty sure there is something wrong. Very scary as well.

Because, if any of the ExecDQL runs accidently and updates something or deletes somethings??

All you have to do is to run the following script;

define "tN" Number .

tN := MemoExecDQL (any DQLStore with (DQLNo = 015) DQLScript , "" , "" , "" , "" , "") .

As you will see, this script wants to run 015 from the DQLStore. But, it is not happening.

What am I doing wrong here?

Regards

Arul 

Hi Arul.

I played with your problem a little.

0. General ;-) All support is based on latest released version of the product. Before contacting support, the problem should always be tested in the latest release version first.

1. The problem is not MemoExecDQL() but the relationship.

2. I didn?t have the problem with your DQL which worked out of the box in 1700, but I am sure this is not related to your version as this is bog standard functionality.

I used your DQL 1 to test:

define "tN" Number .

tN := MemoExecDQL (any DQLStore with (DQLNo = 015) DQLScript , "" , "" , "" , "" , "") .

define "tN" text .

define "tDQLNo" numeric string 3 .

tDQLNo := 15 .

message "Running ExecDQL 001" window .

tN := MemoExecDQL (any DQLStore with (DQLNo = tDQLNo) DQLScript , data-entry field2 , "" , "" , "" , "") .

By mistake I put in DQL 15, and it didn?t fire.

So changed it to 015 and it worked.

Numeric string is numbers as text so 15 would be 150 rather than 015 etc.

There is known problem with Numeric Strings, in this sample I fixed it simply by using Number as datatype for tDQLNo.

But the problem is not ExecDQL but the Relationship so that is where you need to start looking.

A good way to know if it is the DQL or the relationship is simply to execute the DQL in question in situ. If it works there, it will be the way it is read etc.

Thank you for taking your time to check this out.

In regards to the latest version, it is not always possible to keep the application updated.

When you (as a vendor) cannot provide guarantee everything in the application will work after upgrade.

It is not like going from Windows 95 to Windows XP. Which I can understand it is a major upgrade needs full testing.

But, going from 8.2.0.1619 to 8.2.0.1700 needs full testing of an application too!

In my experience, I have always seen something fails after update. Also it will be hard to keep up with your releases.

I can’t go back to my clients each week or every month and say they need to update.

Then if something fails, they will hang me.

So, I am very caution about updating live/production databases.

Coming back to the issue, as I explained this has happened to me twice so far with two different customers.

Unless you misunderstood the issue. When you say it is a problem with the relationship, I am not understanding.

How can that be a relationship issue when we use ad-hoc relationship like;

tN := MemoExecDQL (any DQLStore with (DQLNo = 015) DQLScript , "" , "" , "" , "" , "") .

Simply based on this line, I want the script to find ‘015’ NOT ‘001’ !!!

Unless I am missing something here.

All relationships are ad-hoc as such, the difference is only how they come about i.e. from a stored table or in a stored script or properly ad-hoc like in ExecDQL…

Anyway, what I say is that the problem is that the relationship doesn’t hit, not that there is something wrong with it as such.

So!

1. There is nothing wrong with MemoExecDQL()
2. There is something wrong in the “lookup” i.e. the MemoExecDQL do not get fed with the correct script.

Solution: Change the key to text or number or something. Obviously it has some problems with your Numeric String.

I don’t say that you have to convert your customer to the latest version, but you need to test the problem in the latest version before you report it.

Why?

1. We can’t do anything with bugs in older version, so it is a waste of everybody’s time if it works fine in the latest but is not working in the older version.

2. Any fix will be an increment on the latest version so if you won’t upgrade there is no fix… ;-)

I am still puzzled why it fails when I call it directly like;

tN := MemoExecDQL (any DQLStore with (DQLNo = 015) DQLScript , "" , "" , "" , "" , "") .

BUT, it works when I do something like this;

tN := MemoExecDQL (any DQLStore with (DQLNo = 001) DQLScript , "015" , "" , "" , "" , "") .

Where first record will say something like this;

define "tN" Number .

tN := MemoExecDQL (any DQLStore with (DQLNo = data-entry field1) DQLScript , data-entry field2 , “” ,”” , "" , "") .

Basically, I am telling MemoExecDQL to use the first script and first script will call the ‘015’.

This works fine!

In regards to changing from numeric to text. I have tried it with my first customer, it does not work either.

Only thing works is, if I use the first record in the DQLStore to run other scripts like I showed above.

We have tested all of these cases, and all work. We haven't tested it in1619 though but in 1700.

Again we need to state that the problem is with the lookup/relationship and not with MemoExecDQL(), if you tried to lookup the value rather than execute it you would get the same problem.

Have you tested this in 1700 and been able to replicate the problem? If so please advice how.