I'm using Outlook 2003 (running on Exchange) and the June 2004 version of Outlook Connect. I'm synching with a MySQL server.

When I create a new record (contact) in Outlook, then try to store it to the MySQL database, I get the error "Could Not Set Field Information. (SyncFolder)".

If I go manually into the record and populate the fields OCPRIMNAMES and OCPRIMVALUES, Outlook Connect then stores the record to the MySQL database with no problem.

The Outlook contact list was created in an earlier version of Outlook. My PST and OST files were transfered to the new machine and imported (converted?) by Outlook 2003.

Any suggestions on what I need to do so these fields will auto-populate?

Thanks-

-Did you had the same problem before the conversion of pst/ost?
-Please check the primary key settings (Assign table dialog) and the statement used for
creating new primary key value

I did not detect the same problem prior to the conversion, however I did not fully utilize OC at that time as I knew a conversion was pending. It was only tested a couple of times, but I don't believe the problem existed. I understand the conversion is from ANSI to UNICODE format. I do not have the option of reverting to ANSI format.

I have tried a couple of different primary key settings statements, including a simple "Select "1'"" in order to test with a single record. The current statement is "Select newid()". I have also used "select hash(now())". The same error consistently occurs.

The primary key is assigned to object_id. The other two mandatory keys are owner_id and object_type, select ("david") and select("object") respectively.

Second thought- OC must have worked successfully before the conversion. That's the way the OCPRI fields got populated on all of the pre-conversion records which were imported.

Adam, can you send us your database with some test data in it and also your .pst with some contact examples in it, we can try to debug it.

(Also in Assign Table dialog use the export button to generate ini file and send it to us)

Always helps to make sure the MySQL code is correct. "select hash(now())" should have been "select md5(now())". Perhaps my version of MySQL doesn't support the newid() call, but at any rate it is working now with "select md5(now())". Don't know when during the conversion process I hosed up the code, but obviously I did.

Thanks for the help.