Yes. All it is is a log file of citizen complaints, nothing fancy. The users of one of my apps did not want to have to deal with 2 apps, so they asked me to add the ability in their own app to input data to someone else's Access complaint tracking database.

These things are about as ubiquitous as mailing label databases, so I put in the commensurate level of effort. :)

>So, you allow the trailing spaces to exists on the character fields that you are transfering?
>
>>Just looking at the data in the Access table they are populating, the padded spaces are not causing any problems there. The PK is a numeric and a surrogate. My users can only retrieve and edit their own records, so there is no update conflicts by using Key Fields Only update option.
>>
>>
>>>How do you deal with VFP adding trailing spaces to the Access field values?
>>>
>>>>I use ODBC and remote views to MS Access tables. Works great.
>>>>
>>>>>I can do this much, which gets me a list of the tables in a chosen .MDB file stuck into the ACCTABLES cursor.
>>>>>My goal is to be able to add records to the customer table in the open database, but I guess my SQLEXEC function isn't the way to go about it...
>>>>>How far off am I?
>>>>>
>>>>>sh = SQLCONNECT() && Will ask me what I want to connect to
>>>>>retval = SQLSETPROP(sh, 'Asynchronous', .F.)
>>>>>retval = SQLTABLES(sh, "TABLE", "ACCTABLES")
>>>>>retval = SQLEXEC(sh, [INSERT INTO Customer (firstname, lastname) VALUES ("first_name", "last_name")] )
>>>>>
>>>>>retval = SQLEXEC(sh, "SELECT * FROM Customer", "custcopy")
>>>>>
>>>>>SELECT custcopy
>>>>>BROW && And it's still empty!
>>>>>
>>>>>What should I be doing?
>>>>>
>>>>>Thanx!