Ya que es un char(200) no se exactamente porque te da el error, lo busque en google y encontre varias referencias como la siguiente:
Cita:
community.borland.com
Article #15093: 'Translate error, value out of bounds' error
Question and Answer Database
FAQ93B.txt 'Translate error, value out of bounds' error
Category  atabase (FoxPro)
Platform :Win95/NT
Product :
Question:
"Translate error, value out of bounds" error with blank date
fields: What causes this error and how do I get around the problem?
Answer:
Fox Pro stores one of three things in a date field:
An actual date (ex 19970727 is 7/27/1997)
8 Spaces (ASCII 20)
8 Zeros (ASCII 30)
All of these are acceptable to Fox Pro. The Fox Pro driver for
the BDE only accepts 1 & 2 as valid dates and returns a
translate error for the 3rd (8 ASCII zeros) as it doesn't
consider this as a valid date. To fix the problem, restructure
the date field to a char field and then restructure the table
again changing the char filed back to a date field. This
translation writes back only valid values to the date field and
fixes the problem.
7/15/98 3:23:06 PM
Last Modified: 01-SEP-99
|
Lo que indica que probablemente el error se genera porque hay campos vacios (nil ó null) y cuando los encuenta te genera el error.
Si no es así te recomiendo que busques en google "Translate error, value out of bounds" (con las comillas) a ver si encuentras una mejor explicación.