Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 317 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Using .NET instead ADO ??
gjgarciasm
Member Posts: 47
Hi,
I have used many times ADO - Automation Microsoft ActiveX Data Objects - from Navision code to access to different kinds of databases like Oracle, SQL Server. In fact it is a good strategy to create connectors using transactions to controll data insertions, updates and deletes.
Mi question is that I am new in .NET technology and I am very interested in answering the following:
I have to develop a new conector with several Microsoft Applications. Is there any kind of similar way or procedure to work using .NET automation objects or similar technology instead ADO objects? Any reference will be helpful. :?
I am sorry if the question is a nonsense but I am very new in .NET.
Thank you very much.
I have used many times ADO - Automation Microsoft ActiveX Data Objects - from Navision code to access to different kinds of databases like Oracle, SQL Server. In fact it is a good strategy to create connectors using transactions to controll data insertions, updates and deletes.
Mi question is that I am new in .NET technology and I am very interested in answering the following:
I have to develop a new conector with several Microsoft Applications. Is there any kind of similar way or procedure to work using .NET automation objects or similar technology instead ADO objects? Any reference will be helpful. :?
I am sorry if the question is a nonsense but I am very new in .NET.
Thank you very much.
0
Comments
And .NET 1.1 or .NET 2.0 ?
Hi,
I think the place is not important because for example you can use ADO from a Navision client, old ASP pages, Visual Basic Applications, C++ Applications, etc.
But I need implement this kind of functionality from Navision clients specifically.
Thank you.
Navision (and ASP classic and VBA and lots of other hosts) only talks COM, not .NET, so you cannot use the .NET SQL libraries directly from Navision. You could write your own wrapper around them and make that wrapper COM visible, but that would only add a layer upon a layer and have the side effect that to use that component you would not only have to make sure that MDAC but also the NET framework is installed on any computer you would want to use it. Even worse, when you try to go to the DB, not only would the MDAC component have to be fired up, but also the .NET framework.
The only good reason to ise .NET to connect to SQL is when the software that needs that connection can talk .NET to that connection instead of having to go through COM interop.
So if you need a SQL connection from Navision clients, just use plain old ADO, there really is no point in using .NET SQLAdapters and DataSets.
I've explore and search for automation that support .NET database component like datareader,datadapter,etc... but until now I can't find that component....
but I heard that CFRONT in NAV4.0 SP1 has changed into CFRONT.NET, I think it can talk to another window app and web app that is develop under .NET tech....
CMIIW....
It's been said before... Navision doesn't know how to talk directly to .NET, it has to be COM compatible. If you have working code, why change it? Just so you can say you are .NET compatible?
RIS Plus, LLC
I conclude of your interesting information that programming C/AL code to connect to external datasources through .NET technology may be posibble but it is only worthy if you are obliged to do it. For example, If you have other .NET application and you have to access it.
It is curious to read this words because I have loosen two possible and important customer firms - with very technician people in their staffs from old SAP partners usually - only by this cause in the last two months. I mean, I am 5 years experience tehcnician in Navision with complex, reliable, and demonstrable implementations, but this kind of firms want to have the state of the art in technollogy :?
My next goal, for example, is to define a new connector with Retail Management System and I want to avoid plain or XML files transfers. My first intention was to develop a new module in NAvision using ADO - as I said before I am very experienced with ADO against SQL Server and Oracle - to connect Navision with SQL Server HQ database.
I only wanted to check about other methods.
Thank you very much.
So if the component (database, MSMQ, ...) you are trying to connect to can talk COM, use it directly in Navision. That will be the most efficiënty because Navision does not have to rely on a translator (COM interop) to communicate.
If that component does not talk COM but does talk .NET, you can write a wrapper and make that COM visible. But remember that when you do that COM interop translates all communication from Navision to your target component.
If you lost clients because they want you to talk from inside Navision to SQL Server through .NET, then they really are not that a great loss. It are clients that do not understand technology but have big assumptions about it, they would only mean trouble.
RIS Plus, LLC
Yes. I like to share and learn with the best masters
Don´t worry. I´m sure you have more and better customers than me.