On Wed, 2007-10-10 at 12:01 -0400, Gauthier, Dave wrote:
> > -----Original Message-----
> >From: pgsql-general-owner@postgresql.org
> [mailto:pgsql-general->owner@postgresql.org] On Behalf Of Scott Marlowe
> >Sent: Wednesday, October 10, 2007 11:23 AM
> >To: Ow Mun Heng
> >Cc: pgsql-general@postgresql.org
> >Subject: Re: [GENERAL] pgodbc + Excel + msquery + background refresh
>
> >On 10/10/07, Ow Mun Heng <Ow.Mun.Heng@wdc.com> wrote:
> >> Just wonder if anyone here uses Excel to connect to PG via ODBC.
> >>
> >> I'm using it extensively as my platform to get data from PG/MSSQL
> >> directly into excel. (Excel uses the msqry32.exe file which is like a
> >> stripped down sql query tool and returns data directly into excel)
> >>
> >> When using mssql, connecting from excel to mssql, I can get the query
> to
> >> run in the background. Hence, a long running query will not interfere
> I have. Wasn't that tough. I used the ANSI ODBC Driver (psqlODBC). In
> Excel, I embed a macro that runs a query against the DB. I let the "New
> Database Query" (via Data -> Import External Data) tool figure out the
> connection string. And I also use an extension called QueryEditor (I'll
> try to attach) to code the query. The stuff MS provides with regard to
> query development is pretty crude and limited. QueryEditor is much more
> accommodating. So you basically let "New Database Query" make the
> connection to the DB (select anything from any table doesn't matter),
> then edit the query (change it altogether) using QueryEditor. I use it
> to make plpgsl function calls.
Thanks for the code..It came through. But unfortunately, it suffered
from the same fate. It's not asyncrhnous. Meaning, it hangs up excel
during the query. This is an issue because , well the long and short of
it is that it Hangs up Excel. Hence it's not a solution at all.
I've sent this same email to the odbc list, but seems like either it's
very low activity or, not many people uses odbc to connect to PG (or via
excel for that matter)
