Re: Windows application deployment

Thanks... I was wondering about the difficulty of an OLE DB provider for
Postgresql...

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Clark, Joel" <jclark(at)lendingtree(dot)com>
To: "'Adam Lang'" <aalang(at)rutgersinsurance(dot)com>;
<pgsql-interfaces(at)postgresql(dot)org>
Sent: Monday, October 16, 2000 5:07 PM
Subject: RE: [INTERFACES] Windows application deployment

> This is kind of off-topic, but I am starting on a native OLEDB provider
for
> ADO. This would eleminate the ODBC driver issue. No ECD yet...
>
> To answer your question, you can do a ::CreateProcess() and then
> ::WaitForSingleObject() on the HINSTANCE that comes back in
> lpProcessInformation->hProcess. The Win32 subsystem will signal the
handle
> when the process dies, which triggers WaitForSingleObject() to return. If
> it is an InstallShield installer, then that won't work because install
> shield spawns another process and then kills itself. Hope this helps.
>
> jc
>
>
> -----Original Message-----
> From: Adam Lang [mailto:aalang(at)rutgersinsurance(dot)com]
> Sent: Monday, October 16, 2000 4:57 PM
> To: pgsql-interfaces(at)postgresql(dot)org
> Subject: [INTERFACES] Windows application deployment
>
>
> I assume some people have written windows based applications for a front
end
> to postgresql. I have a VB app that uses ADO to conenct to the odbc
driver
> of postgresql.
>
> The question I have is, has anyone done something for the install (either
> using package and deployment or windows installer) to automate the
> postdrv.exe isntall along with the normal application? I was thinking
about
> having the setup fire off the postdrv install, and then modify the
registry
> for the ODBC data source, but was hoping someone else hs already done
> something along this lines.
>
>
> Adam Lang
> Systems Engineer
> Rutgers Casualty Insurance Company