Ah some bad memories never really go away. About a year ago I had this perfectly lovely form with lots of fields to when I added one more started getting 1812 statement too long. Finally I got a response from a MS contact thru compuserve. I'll try to find the exact text but the problem is how the tokenization (word?) occurs for the sql statement. For example, a field name may tokenize to 1,2,n chars; a literal to usually 1. The specifications state the a sql tokenized string may be upto 2K (if memory serves) but........ 1/2 of this is used to built the token string so about 1k is really available and the great part of the reponse was that tokenization is order dependent and therefore the actual max size is INDETERMINATE.

I broke the form into smaller pieces an have avoided lots of fields on a single form like the plague since then. Since all of our apps made need to be upsized to remote ODCB source this has proved to be the safe path.

I'll look in my archieves for the message -- the INDETERMINATE part at the end was the gem!