Fullscreen problem with NAV 4.01 and SQL 2005

patric

Hi,

we found a critical bug under SQL 2005 with the following procedure:
For example:
2 Tables 2 Forms (55000 and 55001)
Navision and Form 1 is opened in fullscreen mode.
Logged User is neither dbowner nor serveradmin, just a normal user.

A command button on Form 1 runs the following C/AL command:
OnPush()
Table1.INIT;
Table1."Entry No." := 1;
Table1.INSERT;
Table1.Description := 'text';
Table1.MODIFY;

FORM.RUN(55001);

expected result: new entry in table1

If you press the button on form1 and then close the appearing form2 and form1, the table1 is empty.

If you run this scenario in window mode the entry is created in table1.

Highlight isn't it?

Kind regards
Patric

kriki

[Topic moved from Dynamics NAV forum to Navision forum]

kriki

Are you sure it is a SQL2005 problem? And that the others don't have the problem.
If you try a COMMIT and a FORM.RUNMODAL instead of a FORM.RUN, I think it will be correct.
I think it happened because you didn't finish the transaction and run a another form.

patric

kriki wrote:

Are you sure it is a SQL2005 problem? And that the others don't have the problem.
If you try a COMMIT and a FORM.RUNMODAL instead of a FORM.RUN, I think it will be correct.
I think it happened because you didn't finish the transaction and run a another form.

Don't think so, it's working with SQL 2000 and it's also working with dbowner/Sysadmin rights under SQl 2005.
Also having different results in fullscreen mode and window mode seems not to be a coding problem as using a "Commit" is also no solution.

kriki

patric wrote:

Also having different results in fullscreen mode and window mode seems not to be a coding problem as using a "Commit" is also no solution.[/b]

And putting the record also in a temptable and running the form on the temptable?

patric

Thanks Alain, but I'm not searching for a code solution as there are a lot of.
This behaviour is definetly an error in the finsql.exe of Navision and a code review and rework is also no solution for a so called compatible wih SQL Server 2005 solution. I'm wondering why this error hasn't been posted so far neither her nor to the MBS support.

Has anyone made the same experience on SQL 2005?
We already tested the internal hotfixes and updates for the client without success. Checked dbproperties without having found a hint.

CYA
Patric

kine

If you are using MS SQL 2005, use 4.00 SP2 with update! There are many bugs in SP1 connected to SQL 2005.

patric

We have are already tested this scenario with SP2 including the updates without success. Scenario still is the same. :roll:

kriki

Did you also install the bugfix of the client of 4.00SP2.
Yesterday, we had a problem with a report that on my PC worked well. It turned out my colleagues used an unfixed version of 4.00SP2 client.

kine

Hmmm, have you reported it to Microsoft?

patric

Yes already reported as critical but without a useful response so far, might end in a new hotfix....

kine

Have they accepted it as a Bug? Were they able to reproduce the problem?

patric

MS is working on it. If I have news regarding this issue I'll write here.

meisterw

We have the same bug.
Are there any news or solutions?

kine

Yes, use newer client.