Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 451199FBD15 for ; Tue, 8 May 2007 11:12:18 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 85148-04 for ; Tue, 8 May 2007 11:12:11 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.239]) by postgresql.org (Postfix) with ESMTP id DD5349FBD2C for ; Tue, 8 May 2007 11:12:09 -0300 (ADT) Received: by wx-out-0506.google.com with SMTP id i28so1678307wxd for ; Tue, 08 May 2007 07:12:08 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:in-reply-to:thread-index:x-mimeole; b=axJjG1UK5BNbq2z14+cTIUaZMlx4Wg5xm96/KCY8hCxRtfHXSgALuKrbjCb5Af6uw4494uXgGd0zHdnWDayTu7Dee/4YxwzFkuhOh4KDgjiVrGOIwxBHatpPAo8RCKF5nAw4/pYxdLhgU40DcOZt/mXZlfarkqGLFwCPJo9jCP0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:in-reply-to:thread-index:x-mimeole; b=gGZnKWax/V7I5ykGrVL7BSnTBso4XA3SWOhqJUbmCRpzU0e8Gp8/l7DWqFwd0dgt0S7CKVy0L3YyVhZbF2Kupu4cpYUJI0QVwNpqyvoceWc6pPNMcEbSmIjXbqsVbUNVKVxKui2XFML1D2hKHz94UCoWexzDUKwMw25FpqEFzLY= Received: by 10.90.120.13 with SMTP id s13mr6215120agc.1178633527173; Tue, 08 May 2007 07:12:07 -0700 (PDT) Received: from mis06 ( [205.214.220.146]) by mx.google.com with ESMTP id i5sm7055915nzi.2007.05.08.07.12.04; Tue, 08 May 2007 07:12:06 -0700 (PDT) From: "Rommel the iCeMAn" To: Subject: Re: Error: Input string was not in a correct format Date: Tue, 8 May 2007 10:10:14 -0400 Message-ID: <003c01c7917a$a87906d0$b364a8c0@theport.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <20667.1178583085@sss.pgh.pa.us> thread-index: AceRBWuivL7xWmoSQpOWlysR3gb+8gAbnbAg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/62 X-Sequence-Number: 28343 Hi Michael & Tom, First of all, thanks to Michael for your response. I did enable logging of SQL queries but still I could find no SQL statements in the logs. This led me to believe it was a client-side error. Then I saw the response from Tom which confirmed what I was thinking, so my second set of thank-you's goes out to Tom. I declared a function as follows: test_func(integer, character varying, integer, character varying). I used Visual Studio's Server Explorer to view the function and it showed up as test_func(integer, integer, character varying, character varying). The problem is that Server Explorer groups parameters together according to data type. If you follow the function declaration according to Server Explorer, you will end up with mismatched parameters. If you follow the function declaration according to pgAdmin, your code will work. From now on, at least until the problem in .NET is fixed, I will be using pgAdmin to view my functions instead of Visual Studio's Server Explorer. FYI, I am using CoreLab's PostgreSQL.NET drivers, I've reported the issue to them as well. At the time I didn't know if it was an issue with the .NET drivers or with PostgreSQL so I reported my findings to this forum as well as theirs. Ok then, that's a mouthful, thanks again guys for the help. Rommel Edwards, Barbados, (sunny) Caribbean.