Re: Conflicts in Relationships

I don't want my software to do any more than what commercially available query builders currently do. Basically they allow users to choose tables and fields and relationships but spare users from knowing SQL syntax.

When users of SQL Server try to configure a relationship in the above example, SQL Server just does the reversal. In MS Access' query builder, it won't make corrections on the user's behalf. It just reports an error - that is what I'm trying to achieve.

Errors should be uncovered during the translation of tables, fields, and relationships (however presented - graphically or otherwise) into SQL syntax. I felt that query builders were a pretty common tool so I thought maybe someone in this group could point me towards some reference material that tells how this is done.

Originally posted by Alan

> The software would need human intelligence. Maybe the single
> "reversal" is

> what is needed to be done to get the "correct/desired" results.
> How would

> the software be able to interpret the semantics of the data/query?

--
Posted via http://dbforums.com