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 1mNzif-0007OR-5m for pgsql-odbc@arkaria.postgresql.org; Wed, 08 Sep 2021 15:42:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mNzid-0000Ze-74 for pgsql-odbc@arkaria.postgresql.org; Wed, 08 Sep 2021 15:42:35 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mNzic-0000ZW-UB for pgsql-odbc@lists.postgresql.org; Wed, 08 Sep 2021 15:42:35 +0000 Received: from mail-ot1-x32a.google.com ([2607:f8b0:4864:20::32a]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mNziU-0000ED-GV for pgsql-odbc@lists.postgresql.org; Wed, 08 Sep 2021 15:42:33 +0000 Received: by mail-ot1-x32a.google.com with SMTP id q11-20020a9d4b0b000000b0051acbdb2869so3540357otf.2 for ; Wed, 08 Sep 2021 08:42:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=YcGK8Oudvxd47jGOLTBuNtfEynnrSD9beGU0R/PsXDs=; b=Axw4LyBkU3c5fa3ZI8z00HihXnaJHW52ULOt5DVGAONLn7bh1UW39hYAhLPCp6KEeA r9TgBPr9vJC9gCnMb7AgPsOiCJ6YKFVIrzxUXkrdu36fAG1ms3wgp6UO1oTPlgZx5PSO N0R/DlPbC75kbqNlbX1Ff9pCluvMu2zw+Dce6eJj8Cgf1vgf0V6DZWJU9oIplybK1J3a RXlVPA03TzSBFpSol+HCzKAA60F2M7vji8tyQ17UWCwhZZpPmIr9Jk617taj4WSgyJnW KFD3tkHGgiZ2+c2PpOLY34vUDfJQuPazNs671Kh4vL8vTbzrURB/Ox6gQthf2pkvUFWn bLzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=YcGK8Oudvxd47jGOLTBuNtfEynnrSD9beGU0R/PsXDs=; b=TK9DmoZR1ZjxhcL619X5GAS1a6C3lNw4rUzgBpcXtfKGr+AvOyIt1sp62khaPG9JQZ ZqqLSqLlRgIN2ZWQEmby62qR05CzHacJFNK0y9QMnxjP37vwozwxvQvd6sxhSqsTqvv7 w9Hduf3VudT33diqYwN1mzIAAqIjH7NtkPwJ7cbHV7I9TSqlyn08l1RGA9yueUhXoKqo N3dNt5oedIt5lZexbFFhGtZXigzdRL8A+8TMZmgcsu7eGZVylPtCwzCh77Qs4dg+iTCf X0o1PNQUAZr8EugsiMS+Vbwtp6IrHQwLr+ksJ7FXQ3DzR0vnzieg6Cpn3hSfLnQxRwWI ecGw== X-Gm-Message-State: AOAM531+AJ1lH05e8ofE/gW71egtoYIyRz+U78IFPnF7yXUZ4vYXwa39 DeJUgsK7KHDC9oCyUlegwfKM3QiqzsA= X-Google-Smtp-Source: ABdhPJyKuCjkA4BfZiWr5eoItWgwd+qwLsG+S068KP56p5RCM3bIbvNOq/aoGXX2nN4fYDz6ojBZHQ== X-Received: by 2002:a05:6830:1213:: with SMTP id r19mr3699566otp.373.1631115745664; Wed, 08 Sep 2021 08:42:25 -0700 (PDT) Received: from [10.71.0.6] ([136.144.43.167]) by smtp.gmail.com with ESMTPSA id u27sm532982otj.6.2021.09.08.08.42.24 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 08 Sep 2021 08:42:25 -0700 (PDT) Subject: Re: Excel ODBC query loosing parameter when returning the query result directly to a pivot table. To: pgsql-odbc@lists.postgresql.org References: From: Danny Severns Message-ID: Date: Wed, 8 Sep 2021 10:42:24 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------8199F7E0CBDF3AD9E69B3012" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------8199F7E0CBDF3AD9E69B3012 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Have you tried looking at the Excel.dmp file that should have been created by the crash. You might also want to look at the windows event log to see if it is any help.  It sounds like a data type mismatch, but that is just a guess. "It's so simple to be wise. Just think of something stupid to say and then don't say it." -Sam Levenson On 9/8/2021 7:34 AM, Andreas Beier wrote: > Hi everyone, > > I am using postgres odbc for quite a while within within excel using > parameters (i.e. using ?s within the query). > > When defining odbc queries in Excel I select "PivotTable Report" > instead of "Table", thus creating a pivot table directly without > having the raw data in an extra sheet. > > Once created, I can alter the query and define parameter (s)linking to > an excel cell. > > Everything works well until I (save and) reopen the file and try to > update: Than my excel crashs. :( > > I did find out, that the parameter definition I defined before is > empty when opening the file. When I do redefine it, everthing works > well again until I (save and) reopen the file and try to update: Than > my excel crashs. :( > > So it's very reproduceable. > > I am using the 32bit driver, latest version and I am running Excel > 2010 and 2016. > > Any idea whats wrong here? > > Thanks > Andreas > --------------8199F7E0CBDF3AD9E69B3012 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Have you tried looking at the Excel.dmp file that should have been created by the crash.  You might also want to look at the windows event log to see if it is any help.  It sounds like a data type mismatch, but that is just a guess.

"It's so simple to be wise. Just think of something stupid to say and then don't say it." -Sam Levenson
On 9/8/2021 7:34 AM, Andreas Beier wrote:
Hi everyone,

I am using postgres odbc for quite a while within within excel using parameters (i.e. using ?s within the query).

When defining odbc queries in Excel I select "PivotTable Report" instead of "Table", thus creating a pivot table directly without having the raw data in an extra sheet.

Once created, I can alter the query and define parameter (s)linking to an excel cell.

Everything works well until I (save and) reopen the file and try to update: Than my excel crashs. :(

I did find out, that the parameter definition I defined before is empty when opening the file. When I do redefine it, everthing works well again until I (save and) reopen the file and try to update: Than my excel crashs. :(

So it's very reproduceable.

I am using the 32bit driver, latest version and I am running Excel 2010 and 2016.

Any idea whats wrong here?

Thanks
Andreas

--------------8199F7E0CBDF3AD9E69B3012--