Does anybody have a description/ documentation of Navision system-tables. (Tables without the Company prefix). Could you please insert a link to a download, or mail me a copy. otto@javit.no
Using Enterprice Manager you find these tables as listed below:
(I should have mentioned th SQL option..)
syscolumns
syscomments
sysdepends
sysfilegroups
sysfiles
sysfiles1
sysforeignkeys
sysfulltextcatalogs
etc...
What I want is documentation describing their function. Some of them are obvious, but especially when using SQL server option I have encountered errors that can be traced to these tables, and it would be convenient to know them better. Also system documentiotion describing Navision inner life would be nice.
regards,
Otto
The tables you mention are no Navision tables but SQL Server tables. They hold the meta data for all SQL Server objects. When you use Navison with SQL Server, then off course they contain all the meta data about your Navision tables as these Navision tables are stored in SQL Server.
These tables are undocumented. It is possible to find info about them on the internet (visit some sites that are all about SQL Server), but Microsoft states that you should not rely on the contents of these tables. It could be that in SQL Server 2005 their contents changes.
Anyway, if you have errors that can be traced to these tables, I would suspect that you did not install Navision properly.
Last of all, we would all like more documentation of Navisions inner life, but it appears that when MS bought Navision they also inherited the tradition of mediocre Navision support when it comes to understanding how Navision does something. The only way you are going to learn about how Navision works internally is by being very good with a windows tracer/debugger.
Object ID Object Name
2000000001 Object
2000000007 Date
2000000009 Session
2000000010 Database File
2000000020 Drive
2000000022 File
2000000024 Monitor
2000000026 Integer
2000000028 Table Information
2000000029 System Object
2000000037 Performance
2000000038 AllObj
2000000039 Printer
2000000040 License Information
2000000041 Field
2000000042 OLE Control
2000000043 License Permission
2000000044 Permission Range
2000000045 Windows Language
2000000046 Automation Server
2000000047 Server
2000000048 Database
2000000049 Code Coverage
2000000050 Windows Object
2000000052 Windows Group Member
2000000055 SID - Account ID
2000000056 User SID
2000000058 AllObjWithCaption
2000000059 Breakpoint
2000000063 Key
it appears that when MS bought Navision they also inherited the tradition of mediocre Navision support when it comes to understanding how Navision does something. The only way you are going to learn about how Navision works internally is by being very good with a windows tracer/debugger.
That is complete and utter nonsense.
In the PC&C days, all of the required information was gained from training classes. These were very detailed, and those that went through them have the grounding needed and understand all of this.
Unfortunately today people want a quick fix and answers now. But that is not how Navision works, and to keep the existing 1.3 million users happy they have to keep new versions compatible with past versions, so its a massively complex task to change the whole paradigm.
Its a pity that people are not willing to invest in training or learning, since that investment in knowledge pays for it self many times over.
Comments
If you mean "virtual tables" (tables you can't see in object designer), have a look at this thread: http://www.mibuso.com/forum/viewtopic.p ... tual+table
Microsoft Dynamics NAV Developer since 1997
MSDynamics.de - German Microsoft Dynamics Community - member of [clip]
(I should have mentioned th SQL option..)
syscolumns
syscomments
sysdepends
sysfilegroups
sysfiles
sysfiles1
sysforeignkeys
sysfulltextcatalogs
etc...
What I want is documentation describing their function. Some of them are obvious, but especially when using SQL server option I have encountered errors that can be traced to these tables, and it would be convenient to know them better. Also system documentiotion describing Navision inner life would be nice.
regards,
Otto
These tables are undocumented. It is possible to find info about them on the internet (visit some sites that are all about SQL Server), but Microsoft states that you should not rely on the contents of these tables. It could be that in SQL Server 2005 their contents changes.
Anyway, if you have errors that can be traced to these tables, I would suspect that you did not install Navision properly.
Last of all, we would all like more documentation of Navisions inner life, but it appears that when MS bought Navision they also inherited the tradition of mediocre Navision support when it comes to understanding how Navision does something. The only way you are going to learn about how Navision works internally is by being very good with a windows tracer/debugger.
Object ID Object Name
2000000001 Object
2000000007 Date
2000000009 Session
2000000010 Database File
2000000020 Drive
2000000022 File
2000000024 Monitor
2000000026 Integer
2000000028 Table Information
2000000029 System Object
2000000037 Performance
2000000038 AllObj
2000000039 Printer
2000000040 License Information
2000000041 Field
2000000042 OLE Control
2000000043 License Permission
2000000044 Permission Range
2000000045 Windows Language
2000000046 Automation Server
2000000047 Server
2000000048 Database
2000000049 Code Coverage
2000000050 Windows Object
2000000052 Windows Group Member
2000000055 SID - Account ID
2000000056 User SID
2000000058 AllObjWithCaption
2000000059 Breakpoint
2000000063 Key
That is complete and utter nonsense.
In the PC&C days, all of the required information was gained from training classes. These were very detailed, and those that went through them have the grounding needed and understand all of this.
Unfortunately today people want a quick fix and answers now. But that is not how Navision works, and to keep the existing 1.3 million users happy they have to keep new versions compatible with past versions, so its a massively complex task to change the whole paradigm.
Its a pity that people are not willing to invest in training or learning, since that investment in knowledge pays for it self many times over.