InfoPath Dev

 I am using IP 2003 (sp1) to design a form that integrates with an Access DB. Recently, the form processor began to throw the following error on Submit: "Multiple colons are not allowed in a name". In trying to isolate the problem I have gone so far as to recreate both the form and the DB -- grrr. This seems to be the key -- one of the tables has 30 columns. When I remove one of those columns (any of them) the form is processed normally. When add a thirtieth column it throws the error.

Surely there is no such limit, at least not such a slight one. Right? Ideas are appreciated. 

Does it matter which column you remove? Will removing any do (first, middle, last)?

I've not done much work with Access in InfoPath, but I would not imagine such a limit existing.

 No. It apparently makes no difference -- I've tried numerous combinations to see if the problem could be further isolated. From the error I had guess that something was causing IP to generate a generic identifier with an extraneous colon along with the gi's namespace identifier. However, I've exported the contents of the form and if there is such a problem I haven't been able to find it in the markup.

 Other ideas?

 Thanks

 

Its probably a runtime issue.

Try building out a new blank form as minimally as possible to do the same submit and see if it persists in the new form. If not, there's something else wrong in your current form. If it does, maybe contact an Access newsgroup/forum to see if anyone there has an idea.

 Yes, I've tried that, and I'm stumped as to why the problem continues. I feel pretty confident -- based on the error -- that this is an InfoPath problem and not an Access one. But, when I have some free time I'll try building a simple one-table, 30 column mdb and see what happens.

 In the mean time, if anyone else can shed some light on the problem, please jump in.

Cheers

 

My suggestion to check with an Access newsgroup/forum was not to suggest that it was a problem with that application, just that someone with a core understanding of that application (with some InfoPath background) might have more insight as to the cause/source of the issue.

Anyone else with ideas -- feel free to jump in at this point.

Good luck!

 Thanks, Greg. I'll give that a try. When I've done some more testing I'll post back with the results in case anyone else runs into similar problems.

 Cheers

 

Thanks! Sorry I couldn't be of more help.

I had the same error but solved it. :)
My Access table had a few fields with (very) long names and some spaces in it. I replaced all spaces by underscores and shortened some names.
After that I could submit again.

Great thoughts--thanks for sharing them. Kerplunk, let us know if this fixes your issue.