John Colby
jwcolby at ColbyConsulting.com
Tue May 9 18:24:02 CDT 2006
Well, I found two "features" today. Working with an ADO recordset to do a "pushbutton" comma delimited file code ("csv" file), I passed in a query name with a dash in it. The code apparently truncated the query name at the dash and actually selected a query that happened to be named the remainder of the name. IOW I had a query called ABCD I had another query called ABCD-XYZ In the rst.Open I passed in ABCD-XYZ. ADO truncated the name to ABCD and opened the ABCD query. QUITE CONFUSING!!! It took me a long time to figure out what was happening. In another case I had a query with a long name. Apparently ADO has some internal limit which treats any string passed in to the rst.open as a query / table name if shorter than X characters but as a SQL statement if longer than X characters. Thus (once I took out the dash) I started getting "not a valid SQL statement, should contain SELECT etc." error messages from my long named query. As soon as I shortened up the query name (removing the dash of course), everything worked just fine. I spent the better part of the day on THAT pair of "features". John W. Colby www.ColbyConsulting.com