MAKEMSI quickly and reliably creates MSI files in a non-programmatic way
Have your say! Join the MAKEMSI discussion list or view archive! Suggest improvements. No question too simple or too complex.
[Bottom][Contents][Prev]: TableDelete[Next]: TableImportFromIdt
Have your say! Join the MAKEMSI discussion list or view archive! Suggest improvements. No question too simple or too complex.
\->Source Code->Commands->TableExportToIdt

The "TableExportToIdt" Command

This command allows you to export some or all tables in a database (in ".idt" format), all binary streams will also be extracted. The "Export to .IDT" facility (or "ORCA") are the easiest ways of manually exporting. You should probably read the "IDT Export Flakey" section.

To extract all files out of CAB files you could unarchive any extracted ".cab" files but its easier to use the installed "MSI MENU... do do this (administrative install).

This command takes these parameters:

EXAMPLE - Import .IDT files

This example is the complete script required to export all tables in a database:

;--- Include the correct support (MAKEMSI.MMH/DEPT.MMH for MSI Creation) ----
#include "OpenMsi.MMH"

;--- Do the work ------------------------------------------------------------
<$Msi "UISAMPLE.msi" ReadOnly="Y">
   <$TableExportToIdt>                               ;;All "normal" tables
   <$TableExportToIdt TABLE="_SummaryInformation">   ;;Output summary information
   <$TableExportToIdt TABLE="_ForceCodepage">        ;;Output database code page information
<$/Msi>


Microsoft awarded me an MVP (Most Valuable Professional award) in 2004, 2005, 2006, 2007, 2008 & 2009 for the Windows SDK (Windows Installer) area.Please email me any feedback, additional information or corrections.
See this page online (look for updates)

[Top][Contents][Prev]: TableDelete[Next]: TableImportFromIdt


MAKEMSI© is (C)opyright Dennis Bareis 2003-2008 (All rights reserved).
Saturday May 28 2022 at 3:11pm
Visit MAKEMSI's Home Page
Microsoft awarded me an MVP (Most Valuable Professional award) in 2004, 2005, 2006, 2007, 2008 & 2009 for the Windows SDK (Windows Installer) area.