I remember having this problem many moons ago. If he used native connections before, the native connection may have not caused the issue on keywords like "table". I know in mysql, you can get around reserved words, but you have to alter every query to use ticks, "select * from `table`" will work, where "select * from table" will blow up.
Here is the nasty part. If you have now found this to not work with this query in xDBC, and it did before with 5.5 and native FMP connection, you may have a larger problem. There may be lots of other reserved words in your schemas, that are going to start showing up all over the place. This is what happened to us, and it was a MAJOR PITA. My suggestion is that you find out exactly what FMP considers a reserved word, then search your schemas for those. -- Robert Garcia President - BigHead Technology VP Application Development - eventpix.com 15520 Coutelenc Rd Magalia, Ca 95954 ph: 530.645.4040 x222 fax: 530.645.4040 [email protected] - [email protected] http://bighead.net/ - http://eventpix.com/ On Mar 6, 2011, at 8:10 PM, Wayne Irvine wrote: > > On 07/03/2011, at 3:07 PM, Robert Shubert wrote: > >> Interesting – “table” may be a keyword in xDBC, of course the error was >> unspecific. >> >> Glad you got it working, hopefully it’ll be clear sailing from here. > > No quite. I still can't get the Search Builder example working. > > Wayne > > > To unsubscribe from this list, please send an email to [email protected] > with "unsubscribe witango-talk" in the body. ---------------------------------------- To unsubscribe from this list, please send an email to [email protected] with "unsubscribe witango-talk" in the body.
