>Gary D. Walworth wrote:
>> Are there any special design considerations when creating reports for use
>> within Emerald?
>> I am currently creating reports in Crystal Reports Pro 6.0. While the
>> reports work well within CR, using them within Emerald returns a cryptic
>> "SQL Server Error" message.
>> I am creating reports that point to the Emerald databse using the 'MS SQL
>> Server' driver. Should I be using an ODBC driver?
>> Any tips or pointers would be greatly appreciated. While we have no
>> using the reports from within CR, we would rather use a single interface
>> access them all.
>I've had challenging times with the SQL Server driver. Using the
>ODBC driver seems to work fine. We only distriubute the ODBC driver
>for Crystal Reports, so if you want to use the SQL Server driver
>on a machine w/out the full CR installed, you have to install
>those components manually.
We do have CR6 installed at each station. The problem seems to be associated
with the 'Select Expert' in CR6. Specifically, when asking for data that
pertains to a specific date range. When using an ODBC connection, the
'Database/Show SQL Query' menu item shows question marks where the start and
stop date should be.
InvoiceItems."InvoiceID" = Invoices."InvoiceID" AND
Invoices."CustomerID" = MasterAccounts."CustomerID" AND
Invoices."Date" >= ? AND
Invoices."Date" <= ? AND
(MasterAccounts."PayMethod" = 'Visa' OR
MasterAccounts."PayMethod" = 'MasterCard' OR
MasterAccounts."PayMethod" = 'Amex')
The error message when using the ODBC driver is:
ODBC error: [Microsoft][ODBC SQL Server Driver]Driver not capable
Followed by a:
SQL Server Error
But, when using the SQL Server driver, the SQL Query looks like:
InvoiceItems.InvoiceID = Invoices.InvoiceID AND
Invoices.CustomerID = MasterAccounts.CustomerID AND
Invoices.Date >= "Mar 1, 1998" AND
Invoices.Date <= "Mar 2, 1998" AND
(MasterAccounts.PayMethod = 'Visa' OR
MasterAccounts.PayMethod = 'MasterCard' OR
MasterAccounts.PayMethod = 'Amex')
And the query runs fine.
In ODBC Administrator, it's showing I am using SQL Server driver version
Do you know if there's a newer version, or has this turned into a Microsoft
Kitty Hawk, NC