PC SOFT

FOROS PROFESIONALES
WINDEVWEBDEV y WINDEV Mobile

Inicio → WINDEV 2024 → [WD20] Strange error
[WD20] Strange error
Iniciado por guest, 05,ago. 2015 18:27 - 2 respuestas
Publicado el 05,agosto 2015 - 18:27
Hi,

i got a new error message in a procedure which worked well until today.
I use hmodify on a file and then an error appears which says it happens in a procedure inittables and i would call a buildbrowsingtable function. But i dont have a procedure Inittables and i dont call buildbrowsingtable, the error appears after hmodify.
If i press Debug in the error window the application is closed, but i can't debug anything.

Any advises?
Greetings


Error at line 22 of Procédure locale InitTables process.
BuildBrowsingTable function called.
The <> data source is not initialized.
- If it is a data file, the file was not found in the analysis or it was not described by HDeclare/HDeclareExternal.
- If it is a query or a view, the execution may have failed.
To retrieve the corresponding error, check the result of HExecuteQuery/HExecuteSQLQuery/HCreateView.

----- Technical Information -----

Project : RechtSo_Gebühren

WL call:
Process of 'Procédure locale InitTables' (Modif.PROCEDURE.InitTables), line 22, thread 0
'BuildBrowsingTable' function, syntax 1

What happened?
The <> data source is not initialized.
- If it is a data file, the file was not found in the analysis or it was not described by HDeclare/HDeclareExternal.
- If it is a query or a view, the execution may have failed.
To retrieve the corresponding error, check the result of HExecuteQuery/HExecuteSQLQuery/HCreateView.

Error code: 70018
Level: fatal error (EL_FATAL)
WD55 error code: 18

Dump of the error of 'wd200hf.dll' module (20.0.115.0).
Identifier of detailed information (.err): 70116
Debugging information:
IEWDHF=1.20
Module=
Version=<20.0.115.0>
Fonction (1,105)
Additional Information:
EIT_PATHWDD :
EIT_PILEWL :
Procédure locale InitTables (Modif.PROCEDURE.InitTables), line 22
Déclarations globales de Modif (Modif), line 24
Procédure globale @@##@@gfCallBackModif@@##@@ (@@##@@CollectionProcedureGlobalModif@@##@@.@@##@@gfCallBackModif@@##@@), line 16
Global Procedure NeueKorrekturrechnungsnummer (Tools.NeueKorrekturrechnungsnummer), line 28
Global Procedure KorrekturrechnungErstellen (Tools.KorrekturrechnungErstellen), line 12
Click BTN_StornierenRechnung (IW_Rechnungen.IW_Rechnungen.BTN_StornierenRechnung), line 57
EIT_DATEHEURE : 05/08/2015 18:17:57

Help

- Check that the file is described in the current analysis.
- For a dynamically described file, check that it has been properly
declared with HDeclare, HDeclareExternal or HDescribeFile.
- For a query created in the query editor, or a query written in
SQL language, check that it has been declared with HExecuteQuery
or HExecuteSQLQuery.
Publicado el 06,agosto 2015 - 11:52
Hi,

after some more testing i can locate the origin of the error:
I have a file "User" which has fields for the last assigned contactnumber, invoicenumber etc.

Every time a new contact is created the last contactnumber is read and the contact gets a new number. Then this field in "User" is incremented and saved (hmodify). I can create as many contacts as i want, it works well.
But then i create an invoice for example. Again the last assigned invoicenumber is read from file "User" and incremented. When the code reaches hmodify(User) the above error occurs.

I can create as many invoices as i want but as soon i create a new contact, the error occurs.
I dont understand why this happens. The code is always the same except the field with the number.

Help please.
Publicado el 06,agosto 2015 - 14:44
Hello Markus

Procedures wrapped in @@##@@ as the prefix and suffix are PCSoft procedures that call the standard Windev WD_Datachanged and WD_Modify test windows.

The most likely cause of the error is probably a faulty file maybe with the Autoid.

If it is a bad Autoid a simple way to fix it is to open that file in WDMap and use Ctrl A to add a couple of records as this will write records with duplicate id's without triggering any errors. Once the Autoid is reset you can delete the duplicate entries.


Regards
Al