G
Guest
I know this issue has been posted a number of times, but I haven't seen any
work around solutions. Perhaps there just isn't any, but if anyone has any
suggestions, here's the issue:
Our office has a number of users who use Access 2003 ADPs to create/modify
views and reports on tables contained in SQL Server. We recently upgraded to
SQL Server 2005, and it appears that APDs can no longer be user to
create/modify views in SQL Server.
How can I continue to provide to our users the ability to create/modify
views and build reports on data in SQL Server 2005 using Access as a front
end? Do I have to convert to MDB's and use linked tables? If so does this
mean that any views users create cannot be stored in SQL Server?
It looks like I'm screwed here, so any suggestions are welcome.
Thanks.
work around solutions. Perhaps there just isn't any, but if anyone has any
suggestions, here's the issue:
Our office has a number of users who use Access 2003 ADPs to create/modify
views and reports on tables contained in SQL Server. We recently upgraded to
SQL Server 2005, and it appears that APDs can no longer be user to
create/modify views in SQL Server.
How can I continue to provide to our users the ability to create/modify
views and build reports on data in SQL Server 2005 using Access as a front
end? Do I have to convert to MDB's and use linked tables? If so does this
mean that any views users create cannot be stored in SQL Server?
It looks like I'm screwed here, so any suggestions are welcome.
Thanks.