What NAV is using is unknown. Probably oledb. It's all inbedded in the C/SIDE clients, which you connect to the SQL database... . The file ndbcs.dll connects to the database, translates to SQL statements, ... .
Furthermore ... the C/AL code you write is stored in the object table ... in the BLOB field. So the entire application is stored in the database, and that's what makes it easy to deploy customizations.
NAV connects to SQL Server via the SQL Server 2000 ODBC driver (regardless of whether you are using 2000 or 2005). It essentially creates a DSN on the fly and the NDBCS.DLL generates the create cursor statements and sends them through ODBC connection to SQL.
Comments
Furthermore ... the C/AL code you write is stored in the object table ... in the BLOB field. So the entire application is stored in the database, and that's what makes it easy to deploy customizations.
Eric Wauters
MVP - Microsoft Dynamics NAV
My blog
thanks
Asier
you can't export the blob content to a readable txt-file. What you get is a binary file (fob).
There are several threads on this forum that handle about this. e.g.:
http://www.mibuso.com/forum/viewtopic.php?t=17702
Eric Wauters
MVP - Microsoft Dynamics NAV
My blog