V10 - ODBC setup

Yahoo Archive
1
The SQL Server Native Client is by default only installed as a part of SQL Server (aka it's installed on the server). Installing the native client on the workstations should get you pointed in the right direction. Mind you there is also a bug in 10.0 that causes the login prompt unless you patch the database via a SQL script because the fields in company config to save ODBC username and password are missing.

Tom Mueller <it@...>
IT Administrator, Iridium Industries
(570) 476-8800

On Sun, Dec 6, 2015 at 8:31 PM, Todd Caughey tcaughey@... [vantage] <vantage@yahoogroups.com> wrote:



I have struggled with exactly this same thing for over a year. I finally resorted to using Logicity Viewer (free).  But even that was having issues until we created a security group to be used in SQL Server like a user and assigned everyone to it. Allows Logicity to run the reports but still can’t run them with the CRruntime from Epicor. CRruntime works fine with the XML based data but of course that’s not ODBC.

-Todd C.

Â

Â

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Friday, December 04, 2015 3:02 PM
To: vantage@yahoogroups.com
Subject: [Vantage] V10 - ODBC setup

Â

Â

Â

We recently converted from V9 to V10 and are having some issues with running custom ODBC based Crystal reports. When I run the report on my client machine with Crystal installed it runs fine. When I deploy it to the menu structure it runs fine on MY client machine. If I run it on another client machine I get prompted for a login.

Â

My client ODBC setup for this report is a System DSN:

Â

Microsoft SQL Server Native Client Version 11.00.5058

Data Source Name: SQL Replication

Data Source Description: Epicor SQL Replication

Server: SQLREPLSRV

Use Integrated Security: Yes

Database: EPICOR10

Language: (Default)

Data Encryption: No

Trust Server Certificate: No

Multiple Active Result Sets(MARS): No

Mirror Server:

Translate Character Data: Yes

Log Long Running Queries: No

Log Driver Statistics: No

Use Regional Settings: No

Use ANSI Quoted Identifiers: Yes

Use ANSI Null, Paddings and Warnings: Yes

Â

If we use the OLE DB (ADO) connection we can run it on any client however when building reports date fields need to be converted to strings vice versa. I read something about the native drivers not being deployed with the report definitions. I don’t want to convert or create reports that I have to convert the dates from string fields to dates within Crystal. Can anyone clarify what I need to do. We did this in V9 and had no issues but we were using Progress and Replication Server (SQL). I suspect I am missing something simple, sucks to get old….

Â

Thanks,

Â

Keith

Â

The information contained in this e-mail message is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or is not the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this message in error, please notify Ferguson Perforating immediately by telephone or reply by e-mail and then promptly delete the message. Thank-you.




2

 

We recently converted from V9 to V10 and are having some issues with running custom ODBC based Crystal reports. When I run the report on my client machine with Crystal installed it runs fine. When I deploy it to the menu structure it runs fine on MY client machine. If I run it on another client machine I get prompted for a login.

 

My client ODBC setup for this report is a System DSN:

 

Microsoft SQL Server Native Client Version 11.00.5058

Data Source Name: SQL Replication

Data Source Description: Epicor SQL Replication

Server: SQLREPLSRV

Use Integrated Security: Yes

Database: EPICOR10

Language: (Default)

Data Encryption: No

Trust Server Certificate: No

Multiple Active Result Sets(MARS): No

Mirror Server:

Translate Character Data: Yes

Log Long Running Queries: No

Log Driver Statistics: No

Use Regional Settings: No

Use ANSI Quoted Identifiers: Yes

Use ANSI Null, Paddings and Warnings: Yes

 

If we use the OLE DB (ADO) connection we can run it on any client however when building reports date fields need to be converted to strings vice versa. I read something about the native drivers not being deployed with the report definitions. I don’t want to convert or create reports that I have to convert the dates from string fields to dates within Crystal. Can anyone clarify what I need to do. We did this in V9 and had no issues but we were using Progress and Replication Server (SQL). I suspect I am missing something simple, sucks to get old….

 

Thanks,

 

Keith

 

The information contained in this e-mail message is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or is not the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this message in error, please notify Ferguson Perforating immediately by telephone or reply by e-mail and then promptly delete the message. Thank-you.

3

I have struggled with exactly this same thing for over a year.  I finally resorted to using Logicity Viewer (free).   But even that was having issues until we created a security group to be used in SQL Server like a user and assigned everyone to it.  Allows Logicity to run the reports but still can’t run them with the CRruntime from Epicor.  CRruntime works fine with the XML based data but of course that’s not ODBC.

-Todd C.

 

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Friday, December 04, 2015 3:02 PM
To: vantage@yahoogroups.com
Subject: [Vantage] V10 - ODBC setup

 

 

 

We recently converted from V9 to V10 and are having some issues with running custom ODBC based Crystal reports. When I run the report on my client machine with Crystal installed it runs fine. When I deploy it to the menu structure it runs fine on MY client machine. If I run it on another client machine I get prompted for a login.

 

My client ODBC setup for this report is a System DSN:

 

Microsoft SQL Server Native Client Version 11.00.5058

Data Source Name: SQL Replication

Data Source Description: Epicor SQL Replication

Server: SQLREPLSRV

Use Integrated Security: Yes

Database: EPICOR10

Language: (Default)

Data Encryption: No

Trust Server Certificate: No

Multiple Active Result Sets(MARS): No

Mirror Server:

Translate Character Data: Yes

Log Long Running Queries: No

Log Driver Statistics: No

Use Regional Settings: No

Use ANSI Quoted Identifiers: Yes

Use ANSI Null, Paddings and Warnings: Yes

 

If we use the OLE DB (ADO) connection we can run it on any client however when building reports date fields need to be converted to strings vice versa. I read something about the native drivers not being deployed with the report definitions. I don’t want to convert or create reports that I have to convert the dates from string fields to dates within Crystal. Can anyone clarify what I need to do. We did this in V9 and had no issues but we were using Progress and Replication Server (SQL). I suspect I am missing something simple, sucks to get old….

 

Thanks,

 

Keith

 

The information contained in this e-mail message is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or is not the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this message in error, please notify Ferguson Perforating immediately by telephone or reply by e-mail and then promptly delete the message. Thank-you.