How to prevent unexpected client version update

rmv_RU
Member Posts: 119
We often use different versions of Nav for different projects. That's why we always use this trigger to prevent unexpected version update:
go create trigger [dbo].[tr_ndo_property] on [dbo].[$ndo$dbproperty] for update as declare @new_identifiers varchar(2000) declare @old_identifiers varchar(2000) declare @new_database_version int declare @old_database_version int select @new_identifiers=identifiers from inserted select @new_database_version=databaseversionno from inserted select @old_identifiers=identifiers from deleted select @old_database_version=databaseversionno from deleted IF @new_identifiers<>@old_identifiers or @old_database_version<>@new_database_version begin raiserror('Client version update is disallowed!', 16, 1) if @@TRANCOUNT <> 0 rollback transaction end GO
Looking for part-time work.
Nav, T-SQL.
Nav, T-SQL.
0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions