Question Working with Access Projects

[kiloez]

Hello all, I've recently worked on a development project that required the use of an Access 2003 Project connected to a SQL Server 2005 backend DB. It didn't take long to realize that there were writing issues to be dealt with. The only way I could do any inserts, updates or deletes was through coding, both in Access, using VBA and ADO, and SQL Server 2005 using sprocs. The VBA code executed sprocs to handle all write tasks. This wasn't the case when I had used SQL Server 2000 on a previous Access 2003 Project. It appears that write functionality has been removed, or is not supported in SQL Server 2005 when using an Access Project. I thought at first it was an issue with the 2003 version of Access, but I see the same behavior when using Access 2007. Is Microsoft fazing out Access Projects in an effort to enforce the use of other development tools like VB.NET, C#? Any feed back would be appreciated. Having to use unbound controls and hand coding write functionality is extremely time consuming.

 

[Pat Hartman]

Microsoft is deprecating the .adp but not so that people will switch to VB.Net, etc. The reason is that the .mdb and .accdb formats work just fine with linked tables and bound forms and because of that, few users ever adopted the .adp format. Since the format had so little use, there was no reason to upgrade it into A2007. That means that it is frozen in time with whatever functionality it currently has. Originally, it wasn't going to work at all with SQL server 2005 but apparently, the team relented and some things will work.

I suggest converting to an .mdb or .accdb if at all possible.