Re: FW: Message for: dpage

From: günter strubinsky <strubinsky(at)acm(dot)org>
To: "'Dave Page'" <dpage(at)vale-housing(dot)co(dot)uk>, <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: FW: Message for: dpage
Date: 2003-03-25 16:38:31
Message-ID: !~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAIKeB5sEQVkOtS/Xf5ulv/MKAAAAQAAAAMIb+KqvSlkCidiRPiXlyZwEAAAAA@acm.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

There seems to be a solution in msiexec itself and I think I am not the only
one who has had problems with missing msi files. This solution is NOT
limited to psqlodbc but to any tool you want to update and don't have the
'old' msi file anymore:

The
-> msiexec /fa h:\...\psqlodbc.msi" <-
worked flawlessly!!! This approach does NOT worl to uninstall something you
have no msi file anymore. Dave's solution is most probably the only way out
there.

Copied From:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechn
ol/winxppro/proddocs/msiexec.asp

As follows:
______________________________________________________________
Syntax
msiexec /f [p][o][e][d][c][a][u][m][s][v]{package|ProductCode}

Parameters
/f
Enables one or more of the command-line options listed in the following
table. Command Description
p Reinstalls only if file is missing.
o Reinstalls if file is missing or if an older version is installed.
e Reinstalls if file is missing or an equal or older version is installed.
d Reinstalls if file is missing or a different version is installed.
c Reinstalls if file is missing or the stored checksum does not match the
calculated value.
>>>>>>>>>>>>>>>>>>>>>>>a Forces all files to be reinstalled.<<<<<<<<<<<<<<<<
u Rewrite all required user-specific registry entries.
m Rewrites all required computer-specific registry entries.
s Overwrites all existing shortcuts.
v Runs from source and re-caches the local package.

package
Name of the Windows Installer package file.
ProductCode
Globally unique identifier (GUID) of the Windows Installer package.


günter strubinsky
<strubinsky(at)acm(dot)org>
Tel: 402.212.0196

> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org [mailto:pgsql-odbc-
> owner(at)postgresql(dot)org] On Behalf Of Dave Page
> Sent: Tuesday, March 25, 2003 9:16 AM
> To: günter strubinsky; pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] FW: Message for: dpage
>
>
>
> > -----Original Message-----
> > From: günter strubinsky [mailto:strubinsky(at)acm(dot)org]
> > Sent: 25 March 2003 15:05
> > To: pgsql-odbc(at)postgresql(dot)org
> > Subject: [ODBC] FW: Message for: dpage
> >
> >
> > So right now I can't uninstall nor install. I don't know who
> > packed odbc into the msi package. S/he probably knows what
> > keys are used.
>
> I did.
>
> How did you use msizap? It should be something like:
>
> msizap T {BD868C41-BB9B-4AA7-A3F1-DB1FA1A02610}
>
> Which works perfectly here. If you have a very old version, it is vaguely
> possible that there is a different product code on your machine. Also in
> the SDK is a program called msispy. Run this (you have to install it
> first), then select 'View Installed Products' from the file menu. It takes
> a minute or 2, but when you get the treeview up, right click and select
> Properties on the offending installation. You can copy/paste the correct
> product code from there.
>
> Regards, Dave.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)

In response to

Browse pgsql-odbc by date

  From Date Subject
Next Message Antonio Reale 2003-03-25 18:15:14 MSSQL --> PostgreSQL
Previous Message Simeó Reig 2003-03-25 15:50:16 Re: Fastest way to read tuples