Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oGCi3-0005RZ-Uf for pgsql-odbc@arkaria.postgresql.org; Tue, 26 Jul 2022 05:02:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oGCi2-0001aQ-UU for pgsql-odbc@arkaria.postgresql.org; Tue, 26 Jul 2022 05:02:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oGCi2-0001aH-Gc for pgsql-odbc@lists.postgresql.org; Tue, 26 Jul 2022 05:02:18 +0000 Received: from mail-qk1-x730.google.com ([2607:f8b0:4864:20::730]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oGChz-0002gf-KM for pgsql-odbc@lists.postgresql.org; Tue, 26 Jul 2022 05:02:18 +0000 Received: by mail-qk1-x730.google.com with SMTP id c3so10263445qko.1 for ; Mon, 25 Jul 2022 22:02:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pcorp-us.20210112.gappssmtp.com; s=20210112; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :thread-index:content-language; bh=cFwpLPJr31B+o+cg6yZwcwUC87eb6+kag4aEpRq9R8E=; b=1AkEPtlvP+ZuBJB9Y3FI/U3zmPkCBF3eI0xwU5YiAQjNfMGjfRoxjmsl6ff2lFmkZ+ P2Pg8qK38bs7mVZJl8DGtMKFhud3jLhufU4FXvC22YHmmuDtQadyLaOD2F3bAg0h1QtD HyOigiAD1ujqQD4x/i/qWWCV3b6zMbvAQsWv3aCiXwu0SFUHeIlDHL497lHfAuZ80Ytz uHQbSNY7+7fEgkoZiiSmh+NNmDXyOvt/1prvq7FqWXPiFoTQ8L5+lGU8nA13tiCHMSgv zpDHvF1+jqug4MDkqMGK/GgKMTJgRcTOnZlvSIPvaeuTgn2ao9ZwPI/XbEdQbAJCm6IS YOzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=cFwpLPJr31B+o+cg6yZwcwUC87eb6+kag4aEpRq9R8E=; b=B1jRcgTvJ/6dzPgSG6CEIf+cvGgLjZpwpMq/QXZZ2cl5Ov/ygEiA5RkSoYN+548/6R 2+jssBt2EJ0jIYNbYD0jnQhF4kdbgskSVNDMK3EcqLeDOLmo1PiUpT+bAGRLp9jbQJS+ hApLoadf9mP6aCizmur6GtPJSh72rJiXeSSbUSm13rQ3Z2wNnOLLHdLaKWE5iAKDkKg/ RJECRJy/Hv/9/iN2TOi+Poo8fDt+jXDS8xK7fptTo35sz9c3dtToKNC0423slmjbg69Y Ttr6eMOuzK0CuM+4Z/t6i8c5fsxRPX2vnheUVkjkPLvMvN0WazEUrq1wX9EmlPg1GdYM vTkQ== X-Gm-Message-State: AJIora821I+9ZHJGr+6QYTNLosrwMj8lDKFpxUIulLHNmQcWFnlL9rR2 jbPdNkypHhsOezB4+A8ZSl2UCNuAoAdNQw== X-Google-Smtp-Source: AGRyM1sAxILi8qMT5rpqbfstAKfCEoyYABPxGyXkemSfCOBTPeGKi3yWfmDokAmPoCMFe8O9wt2zhA== X-Received: by 2002:a05:620a:2a06:b0:6b5:f225:8a4d with SMTP id o6-20020a05620a2a0600b006b5f2258a4dmr11478430qkp.567.1658811733578; Mon, 25 Jul 2022 22:02:13 -0700 (PDT) Received: from F (50-78-240-110-static.hfc.comcastbusiness.net. [50.78.240.110]) by smtp.gmail.com with ESMTPSA id fw8-20020a05622a4a8800b0031eb643c0f5sm8709307qtb.94.2022.07.25.22.02.12 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 25 Jul 2022 22:02:13 -0700 (PDT) From: "Regina Obe" To: "'Taka Taka'" , References: In-Reply-To: Subject: RE: Question for psqlodbc_13_02 Date: Tue, 26 Jul 2022 01:02:11 -0400 Message-ID: <004c01d8a0ac$ddff1310$99fd3930$@pcorp.us> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_004D_01D8A08B.56EE0F50" X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQHywTr+ObK3gJB5+T44DKunzeYkGK1b1dow Content-Language: en-us List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multipart message in MIME format. ------=_NextPart_000_004D_01D8A08B.56EE0F50 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable It depends if your excel is 32-bit or 64-bit. If you are using 32-bit excel then you should use the ODBC 32-bit driver = =E2=80=93 (should show as ODBC Data Source (32-bit) in control panel ) If you are using 64-bit excel then use the 64-bit ODBC driver. (in = control panel this is ODBC 64bit (if you are using a DSN) =20 As I recall I=E2=80=99ve used them with MS Access office 365, so = don=E2=80=99t see why they shouldn=E2=80=99t work with Excel. If you are = seeing a specific error, you should note that as it would help = troubleshoot Note that this file contains both the 32-bit and 64-bit ODBC drivers - = https://ftp.postgresql.org/pub/odbc/versions/msi/psqlodbc_13_02_0000.zip =20 This one is the 32-bit only - = https://ftp.postgresql.org/pub/odbc/versions/msi/psqlodbc_13_02_0000-x86.= zip =20 This one is the 64-bit only -=20 =20 https://ftp.postgresql.org/pub/odbc/versions/msi/psqlodbc_13_02_0000-x64.= zip =20 =20 =20 From: Taka Taka [mailto:takahiko.ito.one@gmail.com]=20 Sent: Tuesday, July 26, 2022 12:48 AM To: pgsql-odbc@lists.postgresql.org Subject: Question for psqlodbc_13_02 =20 I wrote questions bellow. Was my question inappropriate? Could you tell me where to inquire, if so? =20 Hello. I would like to know if psqlodbc_13_02 is compatible with M365. Also, could you please tell me which of the psqlodbc_13_02 would be = suitable to Windows 10 64-bit? =20 Hello. I would like to add some details to my question. The problem is that the tool we were using has started generating = errors. The tool was corresponding to Excel. It is OBDC driver that directly accesses the DB of the system we have applied for and used as individual AP. Since all the use of the ODBC driver from Excel is from VBA, I checked = the operation using ACCESS, but the above individual AP (ODBC driver) could not be referenced. In this event, Office 2016 has been uninstalled, and the individual AP (ODBC) from M365 Excel app is available? On Mon, Jul 25, 2022 at 9:09 AM Taka Taka = wrote: > Hello. > I would like to know if psqlodbc_13_02 is compatible with M365. > Also, could you please tell me which of the psqlodbc_13_02 would be = suitable > to Windows 10 64-bit? ------=_NextPart_000_004D_01D8A08B.56EE0F50 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

It depends if your excel is 32-bit or 64-bit.

If you are using 32-bit excel then you should use the ODBC 32-bit = driver =E2=80=93 (should show as ODBC Data Source (32-bit) in control = panel=C2=A0 )

If you are using 64-bit excel then use the 64-bit ODBC driver. (in = control panel this is ODBC 64bit (if you are using a = DSN)

 

As I recall I=E2=80=99ve used them with MS Access office 365, so = don=E2=80=99t see why they shouldn=E2=80=99t work with Excel. If you are = seeing a specific error, you should note that as it would help = troubleshoot


Note that this file contains both the 32-bit and 64-bit ODBC = drivers - https://ftp.postgresql.org/pub/odbc/versions/msi/psqlodbc_13_02_= 0000.zip

 

This one is the 32-bit only - https://ftp.postgresql.org/pub/odbc/versions/msi/psqlodbc_13= _02_0000-x86.zip

 

This one is the 64-bit only -

 

https://ftp.postgresql.org/pub/odbc/versions/msi/psqlodbc_13= _02_0000-x64.zip

 

 

 

From:<= /b> = Taka Taka [mailto:takahiko.ito.one@gmail.com]
Sent: Tuesday, = July 26, 2022 12:48 AM
To: = pgsql-odbc@lists.postgresql.org
Subject: Question for = psqlodbc_13_02

 

I wrote questions = bellow.

Was my = question inappropriate?

Could you tell me where to inquire, if = so?

 

Hello.
I would like to know if psqlodbc_13_02 is = compatible with M365.
Also, could you please tell me which of the = psqlodbc_13_02 would be suitable
to Windows 10 = 64-bit?

 

Hello.
I would like to add some details to my = question.
The problem is that the tool we were using has started = generating errors.
The tool was corresponding to Excel.
It is OBDC = driver that directly accesses the DB of the system we have
applied = for and used as individual AP.
Since all the use of the ODBC driver = from Excel is from VBA, I checked the
operation using ACCESS,
but = the above individual AP (ODBC driver) could not be referenced.
In = this event, Office 2016 has been uninstalled, and the individual = AP
(ODBC) from M365 Excel app is available?

On = Mon, Jul 25, 2022 at 9:09 AM Taka Taka = <takahiko(dot)ito(dot)one(at)gmail(dot)com>
wrote:

> = Hello.
> I would like to know if psqlodbc_13_02 is compatible with = M365.
> Also, could you please tell me which of the psqlodbc_13_02 = would be suitable
> to Windows 10 = 64-bit?

------=_NextPart_000_004D_01D8A08B.56EE0F50--