Re: MySQL text field lengths truncated
- From: "Guillem" <guillemvicens-nospam@xxxxxxxxxxxxxxxxxx>
- Date: 24 Oct 2006 01:49:24 -0700
Bill Saffin wrote:
Here's the connection string (using TAdoConnection):
Provider=MSDASQL.1;Password=****;Persist Security Info=True;User
ID=****;Data Source=LeoKevinIssues
ok, so you're accessing to MySQL as local database using ODBC, right?
In this case:
- make sure you have the latest MyODBC version. I remember having
serious issues with dates with the last version I used, which was 3.51.
Can't tell if there was any problem with large strings, though. AFAIK
they are testing now version 5.05
- I see you are missing the OPTION parameter in the connection string.
Take a look at the following URLs and check if you need to set any of
the options. Either case, OPTION=3 is a good beginning and won't hurt.
http://www.connectionstrings.com/
http://dev.mysql.com/doc/refman/5.0/en/myodbc-configuration-connection-p
arameters.html
I've connected the field in question to a TDBMemo component. The
first error message I received said it was expecting a memo field but
it was actually a string.
a TDBMemo is well suited for text BLOBs and long alphanumeric fields.
That shouldn't be the issue. How are you connecting it?
--
Best regards :)
Guillem Vicens Meier
Dep. Informatica Green Service S.A.
www.clubgreenoasis.com
--
Contribute to the Indy Docs project: http://docs.indyproject.org
--
In order to contact me remove the -nospam
.
- References:
- MySQL text field lengths truncated
- From: Bill Saffin
- Re: MySQL text field lengths truncated
- From: Guillem
- Re: MySQL text field lengths truncated
- From: Bill Saffin
- MySQL text field lengths truncated
- Prev by Date: Re: ADO vs dbExpress
- Next by Date: Blob fields
- Previous by thread: Re: MySQL text field lengths truncated
- Next by thread: Win98 Locks Access Database
- Index(es):
Relevant Pages
|
|