Sql AutoIncrement How to?

[jorgemir]

Hi. I have a MySql Backend and  have this issue. My Primary Key Field have No Blank or zero validation at Dict level. NetForm does a validation and the response is a valid field error. I can't quit the validation at dict level, because FM3 requires it in order to create the backend autoincrement at the primary key. Any other way to get auto generated field to pass netform validation? Example is guid field, autoincrement and triggered fields at backend level.
Thanks.
Jorge

[Bruce]

Hi Jorge,

>> I can't quit the validation at dict level, because FM3 requires it in order to create the backend autoincrement at the primary key.

I've chatted to Geoff, and we're both not sure that this statement is true. Is there something in the docs that leads you to believe you should do this?

Cheers
Bruce

[jorgemir]

Ok. Not really, but was the only way FM3 creates the autoincrement keys and manages it right when doing a TPS->MySql migration. Docs mentions about Zero/null way to get non-zero and non-blank values at primary keys and I follow this rule at dict validation level, which has proven to be right all the time. Anyway, it would be a major job to get all non-zero or null validation removed in all my 260 files dict!, and a major job to get all those big customer's databases to be upgraded. Some way to get this done at NetTalk? Sort of disable primary key zero validation as an option when this is done by the backend? Seems to me that NetForm does the validation before the data goes to server, so this is the problem....
Thanks
Jorge