Dear Kesav,
I can't say 100%. I haven't done Adobe forms for long months. But I think I know what that could be.
One of the things I used to hate about the forms is the fact that it is an integration of two completely different technologies (ABAP and Adobe) and that means that the "alien" technology does not support everything we are used to. Namely the "syntax check" in this case.
In your case it is probably the fact that your interface structure and your form layout don't match. That often happens when multiple people work on the same thing or when you change your interface and forget to change the form. The system then goes and tries to put the table data into a date time field or something crazy/ incompatible like that.
The problem with this error is that it does not tell you where to go looking. You will have to check the whole form against the interface and look for anything suspicious. This error does not come from ABAP, it comes from the Adobe site, so there is nothing you can do outside of the Livecycle designer to fix this AFAIK.
I would love to help you more, but there is no trace or log you can send for me to get more information. You must find it, fix it, then use the versioning of your objects (that saved my ass several times) and be more disciplined (with your team).
May you don't feel too much pain looking for the problem
cheers Otto
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.