InfoPath Dev

Here you go.  I hope it makes sense.  I am using VB.NET in VSTA to process the Clicked event for a button.  I'm not an all-star coder myself so there are probably better ways but this works.  Regards, Rich  Public Sub CTRL379_7_Clicked(ByVal sender As Object, ByVal e As ClickedEventArgs) Const Quote As Char = ...

Not that you asked, but with my wildcard search, I used a constant to provide the double quotes (this is in VB.NET):   Const Quote As Char = """c" ...strNewCommand = strOldCommand.Replace("as [CasingModelData]}", _ "as [CasingModelData] WHERE CasingName LIKE " & Quote & CasingNam & ...

Given my level of programming skills, my recommendation would be to add in a number of MessageBox.show statements so you can see the value of the string strMySQLCommand.  By doing this, you will be able to see that by appending the where clause at the end of the SQL statement is creating bad syntax.   Add in the message boxes, ...

I ran into the same issue. The problem is that InfoPath adds to the ADO connection query to relate the tables.  For example, in the one I was using, it added "relate [ID] to [System]" after the select command for the second table.  If you just append the wildcard query to the ADO connection command, you'll get the complaint ...