I see no problem with inserting a field in a record when you connect with the DB trough SQL.
However, I do wonder why you're posing such a question on this forum?
If the DB you're speaking of is a NAV db, then I wonder why you are updating it trough SQL.
|Pressing F1 is so much faster than opening your browser| |To-Increase|
Some customers can orders our products on the internet.
If the hade made a order the order goes automatic to sales line and header.
But I can't change or input the Unit Cost LCY.
Is that a problem or is there a possibility to do it a other way?
Maybe if you let the website communicate with NAV instead of directly with the database (plenty of options in NAV, but webservice might be the most convenient).
It's not a problem to communicate directly with the database (although I don't know/care about licensing issues), but if such an implementation is done, then usually the business logic built in the solution is similar to the one in NAV.
But why copy the business logic of NAV if you can let it execute trough Nav? Now it has to be maintained on two (or more) places.
|Pressing F1 is so much faster than opening your browser| |To-Increase|
Comments
However, I do wonder why you're posing such a question on this forum?
If the DB you're speaking of is a NAV db, then I wonder why you are updating it trough SQL.
|To-Increase|
If the hade made a order the order goes automatic to sales line and header.
But I can't change or input the Unit Cost LCY.
Is that a problem or is there a possibility to do it a other way?
It's not a problem to communicate directly with the database (although I don't know/care about licensing issues), but if such an implementation is done, then usually the business logic built in the solution is similar to the one in NAV.
But why copy the business logic of NAV if you can let it execute trough Nav? Now it has to be maintained on two (or more) places.
|To-Increase|