navision 4.00 SP1 findfirst, findlast and findset

GoMaD · 2005-12-12

is it just me or does anybody else have the feeling that the native navision SP1 client is slower than the pre-SP1 client.

Can it be because of the new find keywords (findfirst, findlast and findset)?
It seems that they are reworking the clients to stay closer to the SQL way of working. But this seems to have an opposite effect on the native client.
(if you use the old find('-') or find('+') syntax)

And why is the demo db not altered to use the new find keywords?

or am i just paranoid?

kine · 2005-12-12

1) The new keywords are not used in SP1 in code, because there was no time to use them. They are for future use or when some company need optimalization, than NSC can use this way... or when you are developing something, you can use that...

2) Do not forget, that Navision is developed now only on MS SQL, and you can assume that the performance will be optimized for MS SQL and not optimal for Native DB... :-) they need to sell MS SQL... 8)

GoMaD · 2005-12-12

Kine, thanks for confirming my assumption.

I've just did a find('_') to findfirst and find('+') to findlast conversion of a test db.

It seems that the performance of the native client improves with this change. AND IT'S SO EASY!

DenSter · 2005-12-12

Don't forget that you can't simply replace every instance of FIND('-') with FINDFIRST. You would only do this if you are interested in one record, and you don't have enough information to do a GET. When you intend to loop through data you need to do FINDSET.

GoMaD · 2005-12-12

as I said 'on a test db'

Meaning, as a first test!

navision 4.00 SP1 findfirst, findlast and findset

Comments

Categories