SQL1 or SQL2
Hi,
Using RB Ent 11.06, D2010, ADO, MS SQL Server 2008
I've noticed that many reports converted from BDE/Paradox to ADO, although
they appear OK, are quite often broken with incorrect joins.
e.g. a left outer join has become a regular inner join when you look at the
SQL generated.
I see that if I change the join in the designer with SQL1 setting, they tend
to stay incorrect. If you set it to use SQL type to 2, the example above
works as expected.
Should all reports be set to type SQL2 ? What's the difference between types
1 and 2 ?
Thanks in advance.
Regards, Paul.
Using RB Ent 11.06, D2010, ADO, MS SQL Server 2008
I've noticed that many reports converted from BDE/Paradox to ADO, although
they appear OK, are quite often broken with incorrect joins.
e.g. a left outer join has become a regular inner join when you look at the
SQL generated.
I see that if I change the join in the designer with SQL1 setting, they tend
to stay incorrect. If you set it to use SQL type to 2, the example above
works as expected.
Should all reports be set to type SQL2 ? What's the difference between types
1 and 2 ?
Thanks in advance.
Regards, Paul.
This discussion has been closed.
Comments
Setting the SQL dialect to SQL2 implies that your database supports SQL 92.
By default when the database type is set to SQL Server, the dialect is
automatically set to SQL2. Since you are moving from Paradox to SQL Server,
you will want to be sure this is set as well.
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com