Helps alot --
Thank You very much. I will digest this and see what I can make work..
>From: Richard Broersma <richard(dot)broersma(at)gmail(dot)com>
>Sent: Dec 13, 2010 10:16 AM
>To: "jsilberberg(at)mindspring(dot)com" <jsilberberg(at)mindspring(dot)com>
>Subject: Re: [ODBC] Best way Driver 8.04.01 with Release 9.0
>On Sun, Dec 12, 2010 at 2:58 PM, jsilberberg(at)mindspring(dot)com
>> One small issue I have is that we are now using arrays in the DB and I can't find a way to
>> access them in MS Access 2007 with the OBDC Driver 8.04.01.
>Unfortunately, the ODBC driver for 9.0 wasn't ready at the time of
>release. You can get the 9.0 version here:
>However, since array syntax was a PRE-9.0 feature, it would matter if
>you upgraded to the 9.0 driver.
>> In PostgreSQL the Statement is Select * from table where 1000 = ANY(array_entry);
>> As documented in chapter 8.14.5
>> Tried this syntext in MS Access 2007 with no joy, does anyone happen to know how this
>> should be handled in MS Access read only Selects.
>MS-Access should support this query using either a pass-through query
>or an ADODB result-set. Ordinary queries or DAO results set will not
>Also, how are you passing the "array_entry?" If you are actually
>passing an array to a pass-through query, it might not work. I
>haven't tried it so I don't know, but I would expect it to. If your
>using pass-through queries, it would be better to pass a comma
>delimited string to a query like:
>Select * from table where 1000 = ANY( string_to_array( "1,2,3,4,5,6","," ));
>Although, it seems that and ADODB command can have arrary parameters.
>Which could return a result set directly from an array. Notice:
>Does that help?
>Richard Broersma Jr.
>Sent via pgsql-odbc mailing list (pgsql-odbc(at)postgresql(dot)org)
>To make changes to your subscription:
pgsql-odbc by date
|Next:||From: Jon Erdman||Date: 2010-12-14 18:22:14|
|Subject: Re: Driver version numbers|
|Previous:||From: Richard Broersma||Date: 2010-12-13 15:16:36|
|Subject: Re: Best way Driver 8.04.01 with Release 9.0|