Level 1 exam — WinDev · GUIDINEE.COM

Exam — fresh questions

12 questions to validate the WinDev basics with Yacine, a developer at an electrical equipment trading SME in Oran: creating the analysis (files, typed items, keys, relationships), drawing windows and setting anchoring, writing WLangage (variables, conditions, loops), linking controls to data and handling records, then generating an application with the RAD and customizing it.
Answer everything, then click Check: your score and explanations will appear.

1 · Recall

1. In the analysis, how does Yacine represent a business entity such as “Client”?

He puts it as text in a single large project table to go faster He creates a dedicated file, with well-typed items He saves each customer in an external Excel file that is not linked He duplicates customers in each order to avoid relationships

A business entity = a file, with named and typed items. Each file mixes only one concept.

1 · Application

2. Yacine must store the unit price excl. tax of an electrical product. Which type does he choose?

String, to accept the € symbol and input commas Boolean, to know whether the price is high or not in the catalog Currency, suited to amounts and calculations Date, to date the price in the Produit file

An amount is stored as currency (or numeric): it is essential to calculate, sort and total. Text would make these operations wrong.

1 · Application

3. Yacine wants each order to reference the customer who placed it, without copying their name. How does he do it?

He copies the customer name into an item of the Commande file He creates one file per customer, named after the customer He stores the customer name in a global project variable He adds IDClient (foreign key) in Commande and a Client (1,n) Commande relationship

The Commande stores the customer's key (foreign key), not their name: the relationship avoids duplication and guarantees consistency.

1 · Arbitration

4. A customer changes their name. Which design avoids having to correct this information everywhere?

Storing the name only once in Client and referring to it through a relationship Copying the name into Client, Commande and Facture to go faster Putting the name in an independent file, with no relationship Leaving the name only in memory, without ever saving it

The information lives in a single place (the Client file); the other files refer to it by key. It is then corrected only once.

1 · Recall

5. In a WinDev window, what is a “control”?

An analysis item stored in a data file A line of WLangage code executed when the application starts An interface component dropped onto the window (input, button, table…) An index automatically created on a file's primary key

A control is WinDev's term for an interface component: label, input control, button, combo box, table, tab…

1 · Application

6. Yacine enlarges his input window and the item table stays squeezed in the top left. What does he set?

The window's background color to improve readability The anchoring of the Table control, so it stretches in width and height The type of the Quantite item in the analysis file The primary key of the LigneCommande file in the analysis

Anchoring defines control behavior on resize: the main table is made to stretch to take advantage of the space.

1 · Recall

7. What is the benefit of naming a control SAI_NomClient rather than SAI_Sans_nom1?

It reduces the size of the application's executable file It automatically changes the control's type to currency It enables the control's anchoring over the whole window It makes the code readable and handleable through an explicit name in WLangage

A control is handled by its name in WLangage: an explicit name makes the code understandable and maintainable.

1 · Application

8. Yacine wants to display a message when an order exceeds 10 items. Which structure does he use?

A condition SI Commande.NbArticles > 10 ALORS … FIN A POUR loop that counts the customers in the Client file A call to HLitRecherche without testing the result first A Client (1,n) Commande relationship declared in the analysis

A conditional test is written SI…ALORS…SINON: it is the building block of all business logic in WLangage.

1 · Arbitration

9. To repeat a process a number of times known in advance, what does Yacine choose?

A SI…SINON condition, better suited to process repetitions A POUR loop, with a counter An HFSQL function, designed to repeat a data process A relationship between two analysis files rather than a loop

POUR repeats a known number of times thanks to a counter; TANTQUE is used when the number of repetitions is unknown in advance.

1 · Recall

10. What is ÉcranVersFichier() used for in a linked form?

To automatically generate the whole application from the analysis To delete the current record from the data file To copy the input of linked controls to the items in one go To test whether a search found nothing in the file

ÉcranVersFichier() copies the input of linked controls to the items; FichierVersÉcran() does the reverse for display.

1 · Application

11. After HLitRecherche on a customer code, which reflex does Yacine apply before using the result?

He directly calls HModifie to save execution time He copies the residual memory content to the screen without checking He restarts the RAD to fully regenerate the current window He tests HEnDehors to detect the “nothing found” case

HEnDehors indicates that you are outside the file (no result, or end reached): it is tested before any use.

1 · Arbitration

12. Yacine wants to start his trading application quickly. Which use of the RAD is recommended?

Generate a functional base then add his business rules in WLangage Generate the application and deliver it as is, without customization Code all the windows by hand, never using the RAD Wait for a perfect analysis before even opening the workshop

The RAD accelerates the start by generating a base from the analysis, but the business rules (discount, unpaid invoices, stock) remain to be written.

What's next?

Score ≥ 80%: you master the WinDev basics with Yacine — move on to Level 2 (HFSQL, SQL queries & reports).
Score between 50% and 80%: review the failed sections (1.1 analysis, 1.2 windows & controls, 1.3 WLangage, 1.4 linked controls & records, 1.5 RAD), re-read the course then retake the test.
Score < 50%: re-read the whole level 1 while applying each 48h challenge (Yacine's analysis, Fiche commande window, WLangage discount, form cycle, RAD generation) before trying again.
And after? Keep Yacine's analysis and linked-control reflex: level 2 plugs HFSQL, SQL queries and the report editor into them.