orca isn't showing directory table in uisample.msi
Jim Olsen
Example" has you edit the Directory table in uisample.msi. I found
uisample.msi in "%PSDK%\Samples\sysmgmt\msi\database", made a copy, and
opened it in orca. Orca doesn't show the Directory table (it shows just
24 tables).
For comparison, I opened the file in InstallShield DevStudio and used
Direct Editor to view the contents; it listed Directory in the list of
tables (among others that orca also didn't show).
Any ideas why orca isn't showing all of the tables?
--Jim
Rich [Microsoft Windows Installer MVP]
Jim Olsen <jab...@hotmail.com> spake the secret code
<OPretjLG...@TK2MSFTNGP10.phx.gbl> thusly:
>Any ideas why orca isn't showing all of the tables?
Orca is showing all of the tables, but UISample.msi only contains the
UI related tables. Try merging together Schema.msi and UISample.msi
into a single database and you will have all the tables.
You can also add the Directory table with Orca through the Tables
menu.
--
"The Direct3D Graphics Pipeline"-- code samples, sample chapter, FAQ:
<http://www.xmission.com/~legalize/book/>
Pilgrimage: Utah's annual demoparty
<http://pilgrimage.scene.org>
Jim Olsen
> [Please do not mail me a copy of your followup]
>
> Jim Olsen <jab...@hotmail.com> spake the secret code
> <OPretjLG...@TK2MSFTNGP10.phx.gbl> thusly:
>
>
>>Any ideas why orca isn't showing all of the tables?
>
>
> Orca is showing all of the tables, but UISample.msi only contains the
> UI related tables. Try merging together Schema.msi and UISample.msi
> into a single database and you will have all the tables.
>
> You can also add the Directory table with Orca through the Tables
> menu.
Merging in schema.msi gave me what I needed. The fact that DevStudio
was showing tables that weren't actually in the file made the situation
more confusing than it should have been.
Thanks for the help!
For other newbies, the command to merge:
msidb -d MNP2000.msi -m Schema.msi
--Jim
Rich [Microsoft Windows Installer MVP]
Jim Olsen <jab...@hotmail.com> spake the secret code
<ehO5guNG...@TK2MSFTNGP10.phx.gbl> thusly:
>Merging in schema.msi gave me what I needed. The fact that DevStudio
>was showing tables that weren't actually in the file made the situation
>more confusing than it should have been.
Oh. InstallSUCK Developer Studio. I'm sorry you have to use it!
Stefan Krueger [MVP]
> was showing tables that weren't actually in the file made the situation
> more confusing than it should have been.
I think it's showing all the standard tables, in this case with no rows.
While this makes it easier to add rows (you don't have to create the table
and memorize the column types) it can be confusing in situations like this.
Maybe such non-existing tales should be marked with a different icon.
--
Stefan Krueger
Microsoft Windows Installer MVP
Please post your questions in the newsgroup or vist one of these web sites:
Windows Installer FAQ
http://www.msifaq.com - http://www.msifaq.de
InstallSite - Resources for Setup Developers
http://www.installsite.org
http://www.installsite.de (GERMAN)