Howdy, Stranger!
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
- 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
- 305 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.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
NAS versus C/FRONT
Cristina
Member Posts: 35
For making a data transfer between an other application and Navision (the transfer is needed to do also from Navision to other application and from other application to Navision) what is recommended: Navison Application Server or C/Front?
Also I don’t want to have a Client of Navision open all the time and the tranfered data is possible to do on each second.
Or is another way of a boarding this?
10x
Cristina
Also I don’t want to have a Client of Navision open all the time and the tranfered data is possible to do on each second.
Or is another way of a boarding this?
10x
Cristina
0
Comments
For both options i beleive there is no need for a client to remain active. I never used NAS but it has 1 advantage: it can trigger C/Side code. C/Front can't. So if you want to call navision validation routines i think it is your only option.
If you don't call c/side validation routines then your choice depends on the complexibility of both products. Since i only worked with C/Front i don't now how easy it is to use in comparison with NAS.