>>I have a cgi program that I do not have the source code for. It is writing to a VFP 5.0 database through ODBC. The cgi wants to write a VarChar to my character fields, and as a result, fields are paded with spaces. The cgi program then, of course can not find what it is looking for. It is looking for "test", not "test ". I tried to use a Memo type. This allows the cgi program to read the data, but it can not read the data if it sends other SQL commands. ie. If you type in "test", the cgi program says yes I found it, But if you you say display all the users ("test"), it says "none found". The people who wrote the cgi program are saying that it is a data type problem, and I tend to agree. Has anyboby had any experience with this type of thing? Any ideas would be greatly appreciated.
>>
>>Ed
>
>How did you tell the cgi program to write to a Memo type instead of character type, if you don't have the source code? Does the program allow you to configure the ODBC connection somehow?
>
>In any case, it sounds like back-end VarChar support was an assumption in the CGI coding, and if so, I don't think there's anything you can do, other than choose a database that supports that data type.

I just changed the field type to M. Apparently the ODBC connection resolves this.