....

(sorry, i have troubles logging in)

While testing I encountered the following problem: in our database, timestamps are stored like 20060705160512, but geniusconnect can't replace these, only when I try something like 2006-07-.... any way to avoid this? Maybe a good idea for the next version.

Thanks

Another question:

When a certain field has a value that doesn't match outlook, you just get an error: 'Error item: myname', but I don't see WHY it doesn't work (we have a very big database and i'm trying to see which fields have to be updated), but this way it is just guessing. Is there an overview where it is possible to see which formats are supported?

Thanks.

Hi,

the values accepted by Outlook depend on Outlook version, runing standalone or with Ms Exchange, MS Exchange version etc..., actually this should be documented by Microsoft, but it is NOT. Sometimes it even depends on combination of values, so when Col1 value is X it is OK, but when Col4 value is Y the X is not OK anymore.

I know it is very frustrating, but same here! We have tryed to define some set per column, but we give up!

Thanks, but can't you adapt your software that you can just skip those fields and that in the log the fields who have problems are shown and not just an error message??

Thanks.

Hi,

we don't know what Outlook will/will not accept. Sometime Outlook fires exception during the Save of whole Outlook Item (not during the setting of the Outlook column).
If the exception is fired during setting of an Outlook column we can and will detect it and you will see the column name and the error message from Outlook.

ok, thank you very mutch

conversion problem has been solved in version 3.0.0.9

Latest release:
http://www.geniusconnect...les/GeniusConnect/2/3/4/