Hi all! I’m new to coding on a SQL database and don’t know what I need to do differently. I’ve recently discovered that besides performance, it acts differently. I hate those kinds of surprizes. Any help would be appreciated. Julie
Could you provide us with a specific problem that you’re running into? I haven’t seen code differences between Navision C/SIDE and SQL option, so I’d have to know what exactly your problem is.
This thread http://www.mbsonline.org/forum/topic.asp?TOPIC_ID=5986&SearchTerms=difference,sql,native contains some information…
I am in process of implementing Nav 3.7 on SQL. The idea was that SQL would give me stable DB and my implementation would be steady minus any headaches. But after going thro the comments here, I am having second thoughts. Any suggestions ???
Specifically, I’m in the Sales Order subform, on line one… but the line number does not exist yet. OnAfterInput on the quantity field, I do a SAVERECORD. The (quantity) validate routine on the table checks availablity and possibly changes the location on the line. Then, on the AfterValidate on the form, I do a CurrForm.Update(false). This worked fine in Native, but in Sql it gave me a Rename error message. When I put a SAVERECORD on the validate trigger on the form, it worked fine on both. It took me quite awhile to figure this out. I’d much rather be proactive.
Why not just do a CurrForm.UPDATE(TRUE), this saves the record AND updates the form.
Julie, I can guarantee you that if it behaves differently, then it is erroneous behaviour. There is no intentional functional difference. There are multiuser differences due to different lock and transaction types, and as you mentioned performance differences, but the same code will run on both. The example you gave should be reported as a bug.