Since it is an ADP, all forms and reports will be using either SQL Server views or stored procedures as their data source. Note however that some of those may be SQL T-SQL strings embedded in Visual Basic for Applications that reside behind forms. In your case, I suspect the pivot is actually being done in code behind the form using embedded VBA statements. I do not normally work with .ADP databases, preferring to use the linked table approach used with the .MDB version, so I'm not sure I can be much more help in resolving your issue. I would suggest you post your issue in one of the forums more focused on Access. Those include UtterAccess, Eileen's Lounge in the Access forum, Windows Secrets Access Forum, or in the MSDN Access Developer's Forum.

One of the challenges with .ADP format databases is that you can't easily upload the application in a scaled down version so that experts can tinker with it, since they would also need the SQL Server database. The Microsoft recommendation on what format to use has gone back and forth, but the present recommendation is to use the .MDB format with linked ODBC tables for new development. However with an existing application, I would not suggest redesigning things - I fully expect the .ADP format to be supported in at least the next version of Access.

Wendell

GLMMS, LLC

Evergreen, CO