Re: TEXT datatype and VB6...

There was a quote about a rep of mysql saying postgres has incomplete solutions.
If so, it's NOTHING compared to usoft 'solutions'.

scott.marlowe wrote:
> To add to this, is it possible to set it to varchar(yourlimithere) for
> what you need? My guess is if the limit is very high (over 8192 or so)
> then the DAO methods may break in strange ways.
>
> On Tue, 25 Mar 2003, Dennis Gearon wrote:
>
>
>>microsoft code has a habit of having little nagging problems like this, like,
>>"Oh yeah, you need to make sure to add a space before a command,it's the
>>microsoft way"
>>
>>Not meaning to bash, but I HAD to do some VB programming to access some oracle
>>stuff and do a web page in a class, and the logic and reasoning behind little,
>>extra characters one had to add in queries just galled me, WHY? <grrrr>
>>
>>Not much help to you, I know.
>>
>>I do believe that you're going to find that VB has trouble with that text field,
>>and my (just now) intuition is because it can't handle a variable that has a
>>variable length,without some special effects.
>>
>>Andrew Ayers wrote:
>>
>>>I am posting this to clarify my last email about it:
>>>
>>>First off, this is only happenning when I perform the following sequence
>>>in my VB code:
>>>
>>>Open PGSQL Database (via DSN-less ODBC connection, using psqlODBC driver)
>>>Select Recordset
>>>
>>>With Recordset
>>> .AddNew
>>> ![Field] = "blah" ' Field is a TEXT-type field on the pgsql table
>>> ![Field] = "blah" ' Error occurs here
>>> .Update
>>>End With
>>>
>>>Close Recordset
>>>Close Database
>
>
>