Error when I run a table on a Navision 4.01 DB SQL Server
 
            
                
                    lagiac83                
                
                    Member Posts: 29                
            
                        
            
                    This is a error message that program show:
The xxx TABLE has no ROWVERSION column in the SQL table description.
What can be the problem?
Thanks

LG83
                The xxx TABLE has no ROWVERSION column in the SQL table description.
What can be the problem?
Thanks

LG83
0                
            Comments
- 
            It can only mean that 1) it was not created from Navision, but from SQL 2) or Navision sh**ted itself during creating the table and didn't really finish creating it. I'd suggest to create that table again.
 Do It Yourself is they key. Standard code might work - your code surely works.0
- 
            Thank you...In fact I create the table from SQL...0
- 
            Please forget that as fast as you can Navision's logic is so different from SQL (it's a deeply modified RAIMA engine from somewhere the eighties) that I consider it a complete miracle that they could create an SQL database option. Just look at an oninsert sql trigger on any "entry" table if you like to read horror stories Navision's logic is so different from SQL (it's a deeply modified RAIMA engine from somewhere the eighties) that I consider it a complete miracle that they could create an SQL database option. Just look at an oninsert sql trigger on any "entry" table if you like to read horror stories So, the relation between Navision and SQL is so complicated that it is very important that do not modify anything from SQL. (Reading it from is SQL is OK except that option fields show up as 0,1,2...) So, the relation between Navision and SQL is so complicated that it is very important that do not modify anything from SQL. (Reading it from is SQL is OK except that option fields show up as 0,1,2...)
 Do It Yourself is they key. Standard code might work - your code surely works.0
- 
            so... without all the negative comments...
 Navision treats SQL Server pretty much as a back end only. Maintaining the object is all done from the Navision IDE. The only thing you would typically do in a Navision implementation on SQL Server is maintain the database, work on maintenance plans, do backups, things like that.
 In rare occasions you'd use SQL Server views, but even then you'd be linking those to Navision table objects from the Navision IDE.
 Forget about using SQL Server for any 'real' business logic.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
- 323 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

