Level 2 exam — WinDev · GUIDINEE.COM

Exam — fresh questions

12 questions to validate level 2 with Yacine, a WinDev developer at an SME trading electrical equipment in Oran: HFSQL, SQL queries, reports and reporting, record traversal and WLangage events.
Answer everything, then click Check: your score and explanations will appear.

2 · Recall

1. What is the difference between HFSQL Classic and HFSQL Client/Server?

Classic reads files on disk or a network share; Client/Server goes through a server that centralises access Classic is paid while Client/Server remains free Client/Server cannot run SQL queries on the data, referring to the version's documentation None: they are two commercial names for the same mode

Classic stores data in files on a local disk or network share (standalone/small network); Client/Server installs a real server that processes queries (multi-user, volumes, security, remote access).

2 · Application

2. Yacine needs to speed up product searches by CodeProduit. What is the most cost-effective action?

Duplicate the Produit file into several copies Switch all files to HFSQL Client/Server systematically Index the CodeProduit column Reduce the number of columns in the Produit file

Indexing a frequently searched column is the most cost-effective optimisation: the index greatly speeds up searches and sorts on that column.

2 · Recall

3. In an SQL query, what is the WHERE clause for?

Choosing which files to query Filtering rows by keeping only those that satisfy a condition Sorting the results in ascending or descending order Counting the number of rows in a table

WHERE applies filtering conditions: only certain rows are kept. Placed on the database side, it lets the engine use its indexes and send only what is useful.

2 · Application

4. Yacine wants to display the customer name next to each order. Which query element does he use?

A simple ORDER BY on the customer code A GROUP BY clause on the orders A WHERE filter on the customer code A join (JOIN) between the Commande and Client files

The join combines several linked files: it is indispensable for displaying the customer name next to their order instead of only their identifier.

2 · Arbitration

5. Yacine hesitates between bringing everything back then sorting in WLangage, or filtering in the query. What does he favour?

Filtering on the database side (WHERE): the engine uses its indexes and sends only the useful rows Bringing everything into memory then sorting, because WLangage sorts faster than the database Bringing everything back, because it is equivalent in performance Not filtering, to avoid forgetting rows

Filtering on the database side is infinitely faster: the engine uses its indexes and sends only what is useful, whereas bringing everything back saturates the network and memory only to throw away most of the rows.

2 · Recall

6. In a report, what does the “body” block contain?

The logo and title, repeated on each page The invoice header, printed once at the start The data repeated for each record — the heart of the report The page number, present at the bottom of each page

The body block repeats for EACH record: it is the heart of the report. The start of document prints once, the page header and footer on each page.

2 · Application

7. Yacine wants subtotals per customer in his summary invoice. How does he proceed?

He adds an extra column to the Client file He defines a break per customer (sorted data) and places the subtotals at the end of the break He calculates the subtotals by hand after printing He creates a different body block for each customer

Breaks are the reporting mechanism: a grouping per customer creates a break start block and a break end block where the subtotals go — provided the data is sorted on that column.

2 · Arbitration

8. To produce reliable totals in a report, what is the best practice?

Multiply calculations directly in the report to control everything Enter the totals manually in a free field Avoid breaks and print only a grand total Prepare the data via a query (filtered, sorted) and let the report display and total

The best practice is to prepare the data via a query (filtered, sorted) rather than multiplying calculations in the report: the report becomes simpler, more reliable and more reusable.

2 · Recall

9. Which WLangage loop automatically traverses all records and handles the end of the traversal?

POUR TOUT TANTQUE HEnDehors() = Faux HLitPremier alone, without a loop SI ... ALORS ... FIN

The POUR TOUT loop is the modern and recommended form: concise, readable, it traverses all records and automatically handles the end of the traversal.

2 · Application

10. Yacine displays his catalogue (thousands of references) on screen. Which type of table does he favour?

A memory table filled by TableAjouteLigne to control everything A file table linked to a query, which loads only the displayed rows A temporary table filled by traversing the whole file A succession of input controls rather than a table

For data coming from the database and large volumes, the file table linked to a file or query fills automatically and loads only the displayed rows: it is the mode to favour in management applications.

2 · Recall

11. In which process of a WinDev window do we load data and prepare the screen?

In the window's closing process In the window's initialisation process In the click of the first button encountered In the global declarations, executed first

Initialisation runs when the window opens: that is where data is loaded and the screen prepared. Global declarations only declare the shared variables.

2 · Application

12. Yacine wants to immediately check the quantity entered in an order field. Where does he place this check?

In the click of the Valider button, at the end of the whole form entry In the window's closing process In the Exit event of the field concerned In the window's global declarations

The input check goes in the relevant control's exit: the user gets immediate feedback when leaving the control, rather than waiting for the Valider button click.

What's next?

Score ≥ 80%: move on to Level 3 — procedures, collections, OOP and error handling with Yacine.
Score between 50% and 80%: review the section(s) you failed (2.1 HFSQL, 2.2 queries & SQL, 2.3 reports, 2.4 traversal & tables, 2.5 events), reread the course, then retake the test.
Score < 50%: reread the whole of level 2 while applying each 48h challenge (index a column, write a parameterised query, produce a report with breaks, traverse with POUR TOUT, place a check in a field's exit event) before trying again.
And afterwards? Keep Yacine's HFSQL foundation, parameterised queries, reports and traversals: level 3 connects them to procedures, collections and OOP in WLangage.