Normally, allowed posting period would be controlled by the General Ledger Setup, and only a limited number of users have specific settings - that's the reason for not creating a special job to update all users. In general, it is not recommended to update any tables directly by SQL queries. First of all, because a table can have C/AL triggers that will not be executed this way, and the update can cause data inconsistency. On the other hand, the only trigger in the User Setup table verifies correctness of the entered date, so this update should not cause any issues. But it is always safer to run this kind of updates via C/AL code. I don't know details of NAV 5.0 server archtecture, but in newer versions NAV server tier has its own cache apart from SQL. If a record being updated via SQL, is cached on NAV side, cache will not be refreshed - NAV just does not know that the record gets stale. Not sure though, if it's applicable to version 5.
↧