Problem with Navision 370 A

lagiac83

Hi everyone...

I have a problem with Navision 3.70A

I run a routine, that write into a table and after open a form (that have in source table the table that i have just written).
When i close Navision and I try to launch the same routine or open the form through object designer Navison Crash.
I attach here the identification error and the file navisionInfo.txt:

---

AppName: fin.exe AppVer: 3.70.1.16172 AppStamp:403bf489
ModName: fin.exe ModVer: 3.70.1.16172 ModStamp:403bf489
fDebug: 0 Offset: 00103999

---

Information file prepared 20/10/06 11.48 UTC

Error Class=Exception
Program=Navision (03.70.01.16172)
Operating System=Windows 2000 (5.0.2195)
Total Physical memory=255MB
Used Virtual Memory=56MB
System Locale=1040
User Locale=1040
Global Language=1040
Code Pages=ANSI 1252 OEM 850

---

But the strange things is:
if I re-open the Db, I enter in the Table and delete the all records with F4 the procedure Run, but if I delete all the records via Code at the end of the procedure Navision still crash.
I have tried to change all the form and table properties but none results.

Help me...

Thanks

lagiac83

sorry:

When i close Navision and ReOpen it,I try to launch the same routine or open the form through object designer Navison Crash.

Arhontis

Hi,

What fields do you have in your table? what are the keys? What custom code do you run and where is it? is it in a codeunit?

lagiac83

this is the table PdaFilterTable

Enabled Field No. Field Name Data Type Length Description
Sì 10 Job No. Code 20
Sì 20 PdA Starting Date Date
Sì 30 PdA Ending Date Date
Sì 40 Check PdA Boolean
Sì 41 Check Allocazione Boolean

the key is Job No.

The function is in a Codeunit and this is the code

PdAFilterTable.RESET;
PdAFilterTable.DELETEALL;
IF NOT ((Type=Type::Modello) OR (Type=Type::Simulazione)) THEN
  BEGIN
    REPEAT
      PdANumb := "No.";
      VStartingDate := "Starting Date";
      VEndingDate := "Ending Date";
      VCheckPdA := TRUE;

      IF VStartingDate < TODAY THEN
        VStartingDate := TODAY;

      IF VEndingDate < TODAY THEN
        VEndingDate:=0D;

      PdAFilterTable.INIT;
      PdAFilterTable.VALIDATE(PdAFilterTable."Job No.", PdANumb);
      PdAFilterTable."PdA Starting Date" := VStartingDate;
      PdAFilterTable."PdA Ending Date" := VEndingDate;
      PdAFilterTable."Check PdA" := VCheckPdA;
      PdAFilterTable.INSERT;
    UNTIL NEXT=0;
  END;

PdAFilterForm.SETRECORD(PdAFilterTable);
PdAFilterForm.RUN;

Arhontis

Hello,

I guess your functionality is about creating a table with records that can be used in a form that filters the Jobs...

First of all, I think there is something missing at the NEXT = 0?
Do you have a WITH statement above the code? Why don't you use a FIND before the REPEAT and some filters berfore the find? it should be something like:

vJob.setfilter...... (something like NOT (modelo or simulazione))
IF vJob.FIND('-') THEN
  REPEAT
  UNTIL vJob.Next = 0;

where the variable vJob is from the jobs record...

lagiac83

Mi codeuit is structured so:

OnRun(VAR Rec : Record Job)

If I go into debug, Navisione execute the code that is into trigger OnActivate of the form :

OldStartingDate := 0D;
OldEndingDate := 0D;
OldCheckPdA := FALSE;
PdAFilterTable.GET("Job No.");
PdAFilterTable.FIND('-');
OldStartingDate := PdAFilterTable."PdA Starting Date";
OldEndingDate := PdAFilterTable."PdA Ending Date";
OldCheckPdA := PdAFilterTable."Check PdA";

and after crashes...

I think that Navison find some spurious variables but i don't understand why...

Arhontis

1) For what reason you execute the cu to rebuild the table? Couldn't you do it as a custom procedure inside the Job Rec? The way you have build it, you always get the form run with the last job as current. I don't think this is what you want...

2) Have I understand correctly that your custom table is used as a list of possible filters? or is there some other use for it?

3) When and how do you call the cu? You run it by hand?

4) Why do you set the variables to 0D and then get the filters and reapply values to them?

5) I think that calling the form from inside the OnRun of the cu is not that proper...

6) Do I ask alot of questions?

Arhontis

7) Why do you call both:

PdAFilterTable.GET("Job No."); 
PdAFilterTable.FIND('-');

You should call only the PdAFilterTable.GET("Job No.") or the:

PdAFilterTable.SETRANGE("Job No.","No."); 
PdAFilterTable.FIND('-');

lagiac83

1) Because I select some records in table job and this table has the job no. of the records selected. After i make some opration with this record.

2) The table is used to filter some records of table job but after with this table i Do some other operation

3) The cu is runned after the selection of some records of table job and i run it from another form (Job form)

4) I used the variables after.

5) This is a good idea!! Why it can be a problem?

6) No,no problems...

7) It's true, but it isn't the problem that cause the crash...

Thanks for your time...

Arhontis

Maybe the problem is because you use the OnActivate trigger of the form and not the OnOpenForm...

My overall suggestion is this:

1) Make a list for for jobs so that the user can pick the jobs he wants.
2) Make a function job record that finds and deletes the corresponding record of that specific job in your custom table.
3) With the form of (1) you run that function (2) for each selected record with a loop.
4) Delete the code in the onActivate trigger of your custom form and place it in the OnOpenForm, and clean it up a little and use IF statements in case you don't find the appropriate record.
4) Run your custom form after the loop that creates the records fromn the form (1).
5) So you don't need the cu anymore and I think that implementaion is more clean...

Tell me what you think...

lagiac83

I have tried yet to put the code in OnOpen trigger but Navision still crashes.

The strange thing is that when I Re-open Navision after launch one or more times the routine eand I try to Open the form pressing Run button from object designer Navision Crash !?!

I don't know....

Now I'm thinking about that this problem is a problem of Navision 370...

Arhontis

Take a look at my suggestion, I guess you need a different perspective on that implementation...

Try removing all code from the form you run from the object designer and then try to run it again... And try running the table itself to see if it is crashing because of data or because of the form...

Maybe your table has fields that are not fully compatible with navision, maybe creating the lines you put text into code fields (not uppercased), or have altered the properties of fields and some are not correct, like maybe table relations.

Delete the table and build it again and your form too...

But I strongly suggest you redesign it...