programming languages Online Quiz - 316

A Joiner transformation is used in Informatica when you need to join data from heterogeneous sources, such as combining data from a relational database table and a flat file, which cannot be joined using a Source Qualifier.

Active transformations change the number of rows passing through them. The Sorter transformation is active because it changes the row order. In contrast, Expression transformations are passive (same number of input and output rows), and Lookup transformations can be active or passive depending on whether they're connected or unconnected.

Joiner transformation in Informatica can only join two heterogeneous or homogeneous sources. To join more than two sources, you must use multiple Joiner transformations in sequence, not a single Joiner.

Lookup transformations support three cache types: Static (default, loads entire cache), Dynamic (updates cache during session), and Persistent (cache saved to disk for reuse). These optimize lookup performance for different use cases.

The Normalizer transformation in Informatica is specifically designed to process and read specialized file structures, such as COBOL copybooks, by converting redundant columns into multiple rows.

The RAW datatype is used for binary data that is not interpreted by the database. Unlike Character, Date, or Integer, which can be converted using functions like TO_CHAR or TO_NUMBER, RAW data is generally treated as a sequence of bytes without conversion.

Expression transformation processes data row-by-row without caching. Aggregator, Lookup, and Joiner all require data/index caches for grouping, lookups, and joins. Expression has no cache overhead since it only transforms individual rows based on expressions.

In Informatica PowerCenter, lookup transformations are broadly classified into two main operational types: connected (integrated into the mapping pipeline) and unconnected (called from an expression).

CObject is MFC's root base class that provides serialization support through the Serialize() method and DECLARE_SERIAL/IMPLEMENT_SERIAL macros. Message processing, SDI, and MDI are handled by derived classes like CWinApp, CFrameWnd, and CDocument, not by CObject itself.

In MFC's class hierarchy, CObject is the ultimate root base class from which all other MFC classes derive. It provides core functionality like serialization, RTTI, and diagnostic support. CCmdTarget, CDocument, and CView all inherit from CObject either directly or indirectly.

CObject provides three core capabilities: RTTI (Runtime Type Information) through IsKindOf() and GetRuntimeClass(), serialization support through Serialize(), and diagnostic/debugging support through AssertValid() and Dump(). MDI (Multiple Document Interface) is an application architecture pattern handled by higher-level MFC classes, not CObject.

Windows message prefixes are standardized: WM_ for window messages, BM_ for button control messages, LB_ for listbox messages, EM_ for edit control, CB_ for combobox, etc. DB_ for Dialog Box Messages is not a valid Windows message prefix - dialog boxes use standard WM_ messages or control-specific messages.

WM_DESTROY is sent when a window's non-client area is being destroyed, just before destruction completes. This is the appropriate time for cleanup operations like releasing resources, freeing memory, and destroying child windows. After WM_DESTROY, the window procedure receives WM_NCDESTROY.

OnCreate() is the method that gives physical presence to a frame in MFC applications. It's called when the frame is being created and is where you should perform initialization that requires the window to exist. BeginPaint() is for painting, OnFrame() and CreateFrame() are not standard MFC methods.

LRESULT is the data type used for return values from window procedures in Win32 API. It's designed to handle the various return values needed by window procedures, including handles, boolean values, and other status codes. LPVOID, LPCSTR, and BOOL are not appropriate return types for window procedures.

CFormView creates a view that resembles a dialog box (with form-like layout) while integrating with MFC's document/view architecture. It allows dialog-based UI with document data binding. CScrollView is for scrolling, CEditView for text editing, and CTreeView for tree hierarchies.

Dialog boxes in Windows typically only have the Close (X) button in their title bar, unlike regular windows that may have minimize and maximize buttons. This is by design as dialogs are modal or temporary windows. The statement is accurate for standard Windows dialog boxes.

A Dialog box is a rectangular window resource in Windows programming whose primary purpose is to host, organize, and manage other controls like buttons, text boxes, and labels. Toolbars, menus, and accelerators serve navigation and command execution roles.

In SAS, a single PROC SORT statement can sort only one dataset at a time. The BY statement specifies variables within that dataset, not multiple datasets. To sort multiple datasets, you need separate PROC SORT statements for each.

In Visual C++ (VC++), projects can be built in both Debug Mode (which includes debug symbols and disables optimizations for troubleshooting) and Release Mode (which optimizes the code for production deployment).