Hi Jason, This sounds like an issue caused by MS Access being a lot fussier about column names than ARS. There is a fairly short maximum column name length and many special characters also cause problems. Check the name of the first column that returns the #Name? error.
Including the status history field in the query is often a cause of trouble also. Rod On 30/06/2010, Jason Miller <jason.mil...@gmail.com> wrote: > ** > > Hello everybody, > > > > Here is an odd one. I have a user who wants to connect MS Access 2007 via > ODBC to do some analysis of records. The “SQL” query returns the correct > number of rows but throws an “ODBC -- call failed” error and the three > columns she is asking for return ‘#Name?’ for all rows. I took a server > side API and SQL log and everything checked out there. > > > > She sent me the Access DB she and it worked on my PC with a non admin ARS > user so we focused on her PC. She had the 7.1 patch 5 User Tool which we > upgrade to 7.5 patch 5 during troubleshooting. I also tried with my ARS > admin credentials on her machine with no success. I verified that ‘Replace > “.” in object names’ and ‘Use underscores’ were checked in her ODBC config. > > > > I then remembered that you can run an ODBC trace log. I turned it on, ran > her query again and the correct data was returned. For giggles I turned off > the trace and #Name? was returned. Turn the ODBC trace back on and the > actual data is returned. > > > > Has anybody seen this or have any idea why enabling a trace allows the data > to make its way into Access? > > > > Thanks, > > Jason > > > > App = ARS 7.5 > > App Server =Windows 2008 64-bit > > DB = MS SQL 2005 64-bit > > DB Server Windows 2008 64-bit > > PC = XP Pro SP3 > > WUT = 7.1 p5 and 7.5 p5_attend WWRUG10 www.wwrug.com ARSlist: "Where the > Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
