Figured it out this morning. BAQ automatically filters for current company but I was not in Crystal or Excel via SQL because I did not think our other company had employees entered yet. Hence the duplicated results. Violated #1 rule of reports – always filter for company. My bad.
-Todd C.
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Friday, March 06, 2015 2:17 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Odd EmpBasic Reporting Issue - CR vs. BAQ (E10-SQL)
I posted this on the EUG boards but have had no response. I have an odd issue where if I use Crystal Reports via SQL Server ODBC on the EmpBasic table just to dump out EmpID, Name and PerConID (Person/Contact ID) it shows a lot of people (but not all) with two identical entries but different PerConID. If I run the exact same SQL code in BAQ it only shows people once. All the errant PerConIDs seem to be supplier contacts.
So not sure why Crystal and BAQ are producing different results. If I look in the DB via SSMS it only shows one entry for per employee.
I tried connecting via ODBC with Excel and it too shows two for most employees and the odd PerConID. So looks like the issue is the ODBC connector – the standard SQL Server driver that comes with Windows (7).
Anyone else ever see this or have an idea what might fix it?
Thanks,
Todd Caughey
Business Systems Manager
Dalsin Industries, Inc.
Bloomington, MN