>Hi Christian:
>
>>I use MEDIUMTEXT for memo fields.
>
>>Also, in the mysql.ini file you have to add those lines (restart the service after modifying the file):
>
>
>># Large log files because we use a lot of large fields.
>>innodb_log_file_size=128M
>>innodb_log_buffer_size = 8M
>>innodb_autoextend_increment = 8M
>>innodb_flush_log_at_trx_commit = 1
>>After you changed this, you need to stop the mysql service, then delete the log files (ib_logfile0 and ib_logfile1), and then start the mysql service. >This will rebuild the logfiles so the startup will take a few seconds longer.
>
>>Also, add this line so you can have sufficient connections:
>
>>max_connections = 200
>>And, last but not least, add this line:
>
>># To avoid slow connection because of a reverse DNS lookup:
>>skip-name-resolve
>
>All that??


These are the settings that worked well for me. I have one standard INI file for my MySQL databases which works well in most situations. It takes some time to figure out what works for you, and it can be frustrating at times, but once you have your settings correct you don't need to worry anymore, that's the good part of it.


>Well. The problem is not the field type of database when the cursor transform them as memo fields. The problem is still there. Apparently you can't help converting text fields in database table as text fields in local cursor or table.

That should not happen. Maybe I misunderstood your problem, but can you give me an example whhich query you run and what the cursor contains?

>First I installed the driver as you told me. Then I configured it. Then when I saw the data in the SQLSTRINGCO... instruction is the same of OBDC driver I deleted the "mysql" item and the connection worked well. You perhaps mean if I restart the machine SQLSTRING... doesn't work anymore?

What I meant was that when you change settings in the MySQL ini file, you need to restart the MySQL service, but not the machine, for the changes to take effect. When you restart the machine, the service also automatically starts and the SQLSTRING will still continue to work.