Script running fine - STORE_command makes WHOOM... Plz help

[datanibbler]

Hi,

the title actually says all about my problem, there is no more to it:

- I have an app running once in the morning to query a lot of data from our personell database.

- The data fetched by one of those queries is to be used in two places:

   - It shall be stored just like it is

   - It shall be further processed and the process output should be stored.

The latter actually works well. The former does not - I can't see why: The script runs fine - I've tested by putting the EXIT at different points - and the table gets created. There are no more synthetic keys, no links at all actually, all the other tables are already deleted at that point.

<=> At the very last command, which is a STORE command, copied 1:1 from others (just adapted) creates an error, the entire app crashes (that "failure. Retrieve old data?" message) and the qvd is not created.

The command is

>>> STORE Stempeldaten_gen INTO ..\01_QVD\HR_QVD\Stempeldaten_gen.qvd (qvd); <<<

That command is exactly the same as all other STOREs in that app, the file_path is exactly the same and there are other files with an '_' as well which are created without any problems.

I will attach to this post both

- an excel file with sample personell data

- a sample qvw

[hic]

My guess is that the qvd is locked by another process...

HIC

[datanibbler]

Hi Henric,

good one - but what could lock it? This particular qvd doesn't exist yet, I am about to generate it at that point ... Could it be because there was another qvd written just a second earlier? Can that be a problem? In that case, I could just push the second STORE command to another tab in the script.

[maternmi]

Hi ,

try to store without "(qvd)"

Store Stempeldaten_gen.qvd into [\\........\Stempeldaten_gen.qvd.] ;

Best regards,

Michael

[Anonymous]

Nibbler

I now always put a Sleep(5000) after any Store statement, to thus wait 5 seconds.

This may well be irrelevant to your issue, but since starting doing this I have had no weird issues like you describe.

Best Regards,     Bill

[mr_janne]

First of all you could back up and delete the original QVD files and build them again from fresh.

If that doesn't help you could rename the next generated qvd files in the script.

This way you can test if the QVD file is locked. The QVD file will get locked if the QVW file using it is open.

regards.Janne

[datanibbler]

Hi Bill,

it is just running, I'll have to wait a few minutes - but that might well be the issue I think, so I will try with the SLEEP() command.

Thanks a lot!

Best regards,

DataNibbler

[maternmi]

Hi,

I have a small a mistake

<<<Store Stempeldaten_gen into [\\........\Stempeldaten_gen.qvd.]>>>>

By the way if you already have generated a qvd, then delete it, close QV, open QV and reload your script.

BR

Michael

[datanibbler]

Hi,

unfortunately the problem persists despite all I have tried yet:

- SLEEP 5000 - I have introduced that

- remove the '(qvd)' - I have done that, too.

<=> it doesn't seem to make a difference - the script fails at that point.

[johnca]

What does the script look like just prior to the Store function? Look for extra or missing commas after each field maybe? That's what I usually find in this scenario, especially when I'm storing a resident load and creating the script manually rather than with the wizard.

--john