1 of 6

Microsoft® Business Solutions–Navision® Microsoft® Business Solutions–Navision®

Development I – C/SIDE

Introduction Day 4

2 of 6

Class ScheduleClass Schedule

Monday Tuesday Wednesday Thursday Friday

8:00 Course Introduction (1 hr)

Review (1 hr) Review (1 hr) Review (1 hr) Review (1 hr)

9:00 Introduction to Navision Development (1 hr)

Data Manipulation - MenuSuites (1 hrs)

10:00

11:00 Data Manipulation - Dataports (1 hr)

12:00 Lunch Break Lunch Break Lunch Break Lunch Break Lunch Break

13:00 Architecture - Basic Tables II (1 hrs)

14:00

15:00

16:00

Review Questions (3 hrs)

Data Manipulation - Reports II (2 hrs)

Data Manipulation - XMLports (2 hrs)

Class Review

Data Manipulation - Codeunits (2 hrs)

Integration - Intro & NODBC (2 hrs)

Integration - Automation Server (2 hrs)

Integration OCX (2 hrs)

Architecture - Basic Tables I (2 hrs)

Architecture - Basic Forms I (3 hrs)

C/AL Programming I (3 hrs)

C/AL Programming II (2 hrs)

Data Manipulation - Reports I (2 hrs)

3 of 6

Course Structure – Day 4Course Structure – Day 4

• Course Introduction• Introduction to Microsoft Navision

Development• Basic Design Architecture• The C/AL Programming Language• Data Manipulation• Integration• Review

4 of 6

C/FrontC/Front

• Why use?– Add, delete or view data in your own

applications.– C/FRONT is much faster than using the N/ODBC

driver.

• To use:– To use C/FRONT, you must use some other

programming language such as C++, C, or Visual Basic.

– C/FRONT provides two methods of accessing Microsoft Navision which is either through a C style DLL or through the use of the OCX interface.

5 of 6

C/Front - FilesC/Front - Files

File name Description

cfront.dll C/FRONT C-API library for Navision Server

cfrontsql.dll C/FRONT C-API library for SQL Server

cfront.ocx C/FRONT OCX

cf.h C/FRONT header file

libload.c Source file containing functions to load and unload cfront.dll

dberror.txt Database error/return codes

6 of 6

C/Front LimitationsC/Front Limitations

• Microsoft® Windows ® does not go in to standby or hibernation if there is an open server connection from C/FRONT.

• Entries made by C/FRONT does not fire triggers to execute any code validation.

• Licenses must be correctly loaded on client and server.

• Every connection in C/FRONT is treated as a session. As with regular Microsoft Navision, the client and ODBC, the versions of CFRONT must match the version of the SERVER that you are trying to connect to.

• Only active keys are available to C/FRONT.