pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Windows application deployment
5+ messages / 2 participants
[nested] [flat]

* Windows application deployment
@ 2000-10-16 20:57  Adam Lang <aalang@rutgersinsurance.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Adam Lang @ 2000-10-16 20:57 UTC (permalink / raw)
  To: pgsql-interfaces

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




^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* RE: Windows application deployment
@ 2000-10-16 21:07  Clark, Joel <jclark@lendingtree.com>
  0 siblings, 1 reply; 5+ messages in thread

From: Clark, Joel @ 2000-10-16 21:07 UTC (permalink / raw)
  To: 'Adam Lang' <aalang@rutgersinsurance.com>; pgsql-interfaces

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@rutgersinsurance.com]
Sent: Monday, October 16, 2000 4:57 PM
To: pgsql-interfaces@postgresql.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



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* RE: Windows application deployment
@ 2000-10-16 21:10  Clark, Joel <jclark@lendingtree.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Clark, Joel @ 2000-10-16 21:10 UTC (permalink / raw)
  To: 'Adam Lang' <aalang@rutgersinsurance.com>; pgsql-interfaces

BTW -- For the ODBC DSN creation, see SQLConfigDataSource() and
SQLWriteFileDSN()

jc

-----Original Message-----
From: Adam Lang [mailto:aalang@rutgersinsurance.com]
Sent: Monday, October 16, 2000 4:57 PM
To: pgsql-interfaces@postgresql.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



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Windows application deployment
@ 2000-10-17 12:49  Adam Lang <aalang@rutgersinsurance.com>
  parent: Clark, Joel <jclark@lendingtree.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Adam Lang @ 2000-10-17 12:49 UTC (permalink / raw)
  To: pgsql-interfaces

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@lendingtree.com>
To: "'Adam Lang'" <aalang@rutgersinsurance.com>;
<pgsql-interfaces@postgresql.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@rutgersinsurance.com]
> Sent: Monday, October 16, 2000 4:57 PM
> To: pgsql-interfaces@postgresql.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




^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* RE: Windows application deployment
@ 2000-10-17 13:24  Clark, Joel <jclark@lendingtree.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Clark, Joel @ 2000-10-17 13:24 UTC (permalink / raw)
  To: 'Adam Lang' <aalang@rutgersinsurance.com>; pgsql-interfaces

Not sure how difficult it is going to be.  I may get into it and decide that
ODBC is just fine!  :)

jc

-----Original Message-----
From: Adam Lang [mailto:aalang@rutgersinsurance.com]
Sent: Tuesday, October 17, 2000 8:49 AM
To: pgsql-interfaces@postgresql.org
Subject: Re: [INTERFACES] 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@lendingtree.com>
To: "'Adam Lang'" <aalang@rutgersinsurance.com>;
<pgsql-interfaces@postgresql.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@rutgersinsurance.com]
> Sent: Monday, October 16, 2000 4:57 PM
> To: pgsql-interfaces@postgresql.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



^ permalink  raw  reply  [nested|flat] 5+ messages in thread


end of thread, other threads:[~2000-10-17 13:24 UTC | newest]

Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2000-10-16 20:57 Windows application deployment Adam Lang <aalang@rutgersinsurance.com>
2000-10-16 21:07 RE: Windows application deployment Clark, Joel <jclark@lendingtree.com>
2000-10-17 12:49 ` Adam Lang <aalang@rutgersinsurance.com>
2000-10-16 21:10 RE: Windows application deployment Clark, Joel <jclark@lendingtree.com>
2000-10-17 13:24 RE: Windows application deployment Clark, Joel <jclark@lendingtree.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox