Skip site navigation (1) Skip section navigation (2)

Re: [INTERFACES] [ODBC] Unbound text box, Text > 255 characters, MSAccess/PostgreSQL

From: Zlatko Matić <zlatko(dot)matic1(at)sb(dot)t-com(dot)hr>
To: "Greg Campbell" <greg(dot)campbell(at)us(dot)michelin(dot)com>
Cc: <pgsql-odbc(at)postgresql(dot)org>, <pg-interfaces(at)postgresql(dot)org>,<pgsql-interfaces(at)postgresql(dot)org>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: [INTERFACES] [ODBC] Unbound text box, Text > 255 characters, MSAccess/PostgreSQL
Date: 2005-10-05 20:33:01
Message-ID: 000001c5ca84$8bfa2ed0$52bffea9@zlatkovyfkpgz6 (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-interfacespgsql-odbc
Hello, Greg and thanks for suggestions, but it didn't work with append 
query. I just couldn't pass more than 255 characters long text as parameter 
of DAO query. But, fortunately, I solved the problem by using AddNew method 
of DAO recordset to append new row. In this case I could pass directly the 
whole value of Me.TextBoxName. It seems that in this way Access can pass the 
whole text (as Memo Type) to new row of recordset.
Otherwise if I want to pass the same value of the unbound text box by using 
an append query, it can pass just 255 characters long text.
Fortunately, it works with recordset object...

Thanks,

Zlatko

----- Original Message ----- 
From: "Greg Campbell" <greg(dot)campbell(at)us(dot)michelin(dot)com>
To: "Zlatko Matić" <zlatko(dot)matic1(at)sb(dot)t-com(dot)hr>
Cc: <pgsql-odbc(at)postgresql(dot)org>; <pg-interfaces(at)postgresql(dot)org>; 
<pgsql-interfaces(at)postgresql(dot)org>; <pgsql-general(at)postgresql(dot)org>
Sent: Tuesday, October 04, 2005 3:34 PM
Subject: Re: [INTERFACES] [ODBC] Unbound text box, Text > 255 characters, 
MSAccess/PostgreSQL


What version of Access?
Confirm that Access is interpreting the target field as MEMO, (either look 
at the linked table in design
mode, or use Tools->Analyze->Documenter).
For the query, determine the "type" of the parameter - Query 
menu->Parameters. Be sure you are using type
MEMO.

By the way, 3271 is a Jet error -- Invalid property value.

Good luck.



Zlatko Matić wrote:

> Hello.
> I have the following problem with MS Access/PostgreSQL combination:
> There is a form in Access that has an unbound text box, used for entering 
> a commentary of a batch of records.
> There is a DAO Append Query that has a parameter that is passed from the 
> text box using parameter of DAO QueryDef object.
> I adjusted B7 parameter (Text as LongVarchar) in connection string (ODBC 
> driver) to 1, so that Access links PostgreSQL Text fields as Memo fields 
> in Access. The intention was to be able to enter unlimited length 
> commentary into the field.
> But, although I can enter unlimited text by using bound text box in some 
> other forms, in this particular form I can't use bound control, so I need 
> to pass text from  UNBOUND control to the linked table by using DAO or ADO 
> code. It seems that DAO query can't accept Memo as parameter, but only 
> text. If my text exceeds length of 255, I have an VBA error 3271. If text 
> in unbound text box is shorter that 255 everything is OK.
>
> So, is there any way to pass text of length >255 from unbound text box to 
> Memo field of linked PostgreSQL table, by using DAO or ADO ?
>
> Thanks in advance,
>
> Zlatko



--------------------------------------------------------------------------------



---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings


In response to

pgsql-odbc by date

Next:From: Lothar BehrensDate: 2005-10-06 04:19:04
Subject: Re: Insecurity of ODBC debug logging files
Previous:From: Dave PageDate: 2005-10-05 19:08:12
Subject: Re: Insecurity of ODBC debug logging files

pgsql-interfaces by date

Next:From: Daniel ClaytonDate: 2005-10-09 21:57:37
Subject: Porting embedded SQL from Oracle to Postgres
Previous:From: Jim C. NasbyDate: 2005-10-04 17:36:28
Subject: Re: [INTERFACES] how to monitor dead connections to postgresql database

pgsql-general by date

Next:From: Dennis JenkinsDate: 2005-10-05 21:34:06
Subject: Re: SPI_prepare, SPI_execute_plan do not return rows when using parameters
Previous:From: Andrew SullivanDate: 2005-10-05 20:14:03
Subject: Re: License question[VASCL:A1077160A86]

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group