AnsweredAssumed Answered

queries have to be SQL?

Question asked by njem on Feb 6, 2010
Latest reply on Feb 7, 2010 by njem


queries have to be SQL?



Kind of a beginner question. In access there's that tool for creating queries, not only for sorting or choosing records for a report, but also general data manipulation; select by criteria and then delete a bunch of records or update selected records (scripted, as opposed to the user doing it by find/replace), combine tables, create a new table, saved queries and scripts that let you have queries fed by queries fed by queries, as involved as you want to get. Similar deal on a Paradox project I worked on years ago. FM gives some of this with reports with criteria and summary fields and saved sorts, but seems to be short of what I'm used to. Maybe I just need a shift in perspective on how FM does things. In doing some hunting and reading and tutorial stuff it seems the only way to do this is SQL, which I've never needed to learn. (I suppose I can learn yet another system but I was hoping to not make a career out of this. Just occasional projects.) Am I right in that? And if it's SQL am I right in gathering it can only happen with an FM front-end and an SQL or other back-end, not with and FM back-end? How close to this kind of functionality can I get within FM?